OpenParable
Skip to content
← Back to skills

phx:help

Productivity

phx:help is an Agent Skill for productivity published in the oliver-kriska/claude-elixir-phoenix repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Recommend the right /phx: command for planning, review, debug, deploy, or test tasks. Use when "which command", "what should I use", or "how do I". NOT for /help.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/oliver-kriska/claude-elixir-phoenix/blob/HEAD/plugins/elixir-phoenix/skills/help/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/phx-help, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Plugin Help — Interactive Command Advisor

Helps users find the right command, skill, or agent for their situation.

Usage

/phx:help                          # Analyze context, suggest commands
/phx:help how do I debug this?     # Route to /phx:investigate
/phx:help add a new feature        # Route to /phx:plan -> /phx:work

Arguments

  • $ARGUMENTS — optional description of what the user wants to do
  • Empty = analyze current context (git status, existing plans, file patterns)

Execution Flow

Step 1: Gather Context

If $ARGUMENTS is non-empty, use it as primary signal.

Always gather ambient context (run in parallel):

  1. Check for existing plans: use Glob on .claude/plans/*/plan.md — active work in progress?
  2. Check git status: uncommitted changes? which files?
  3. Check for solution docs: use Glob on .claude/solutions/**/*.md — prior knowledge?

Step 2: Classify Intent

Read ${CLAUDE_SKILL_DIR}/references/tool-catalog.md for the full routing table.

Map the user's situation to one of these categories:

CategorySignalsPrimary Commands
Starting outNo plans, new to plugin/phx:intro
Ideation"explore", "brainstorm", "not sure", "how to approach", "vague idea"/phx:brainstorm
New feature"add", "build", "implement", multi-file/phx:plan → /phx:work
Quick changeSingle file, <50 lines, "fix typo"/phx:quick
BugError, stack trace, "broken", "failing"/phx:investigate
Review"check", "review", PR ready/phx:review
Performance"slow", "N+1", "memory"/phx:perf, /ecto:n1-check, /lv:assigns
Research"how to", "best practice", "evaluate lib"/phx:research
Resume workExisting plan with unchecked tasks/phx:work --continue
Post-fix"that worked", solved a hard bug/phx:compound
Full cycleLarge feature, new domain area/phx:full
Project health"audit", "tech debt", "overall quality"/phx:audit, /phx:techdebt
Dep update audit"audit deps", "supply chain", "post-mix deps.update", "review mix.lock PR"/phx:deps-audit
Manual dep vetting"vet this package", "approve dep", "trust ledger", "after /phx:deps-audit findings"/phx:deps-vet
Deployment"deploy", "release", "production"/phx:verify then deploy skill
Permissions"too many prompts", "allow", "permission fatigue"/phx:permissions
Returning after time off"what did I miss", "back from vacation", "catch up", "what changed while I was out"/catchup (companion plugin, separate install)

Step 3: Respond or Clarify

If high confidence (clear match to one category): Present the recommendation with:

  • The command to run (with exact syntax)
  • One-line explanation of what it does
  • What artifacts it creates (if any)
  • Suggested next step after it completes

If medium confidence (2-3 possible matches): Use AskUserQuestion with the top options, each with a one-line explanation.

If low confidence (vague or no signal): Ask ONE focused clarifying question. Examples:

  • "Are you starting something new or continuing existing work?"
  • "Is this a bug fix or a new feature?"
  • "How many files do you expect to change?"

Then recommend based on the answer.

Step 4: Offer Follow-up

After recommending, always add:

  • "Run /phx:help anytime to get routing advice"
  • If they seem new: "Try /phx:intro for a full plugin walkthrough"

Iron Laws

  1. ONE recommendation — don't dump the full catalog, pick the best match
  2. MAX ONE clarifying question — don't interrogate, make your best guess
  3. Show exact syntax — /phx:plan Add user notifications not just "use the plan command"
  4. Context over keywords — existing plans + git state matter more than word matching
  5. NEVER block — if user already knows what they want, DO NOT redirect

Integration

  • Complements intent-detection (auto-trigger) with explicit invocation
  • References same routing logic but adds interactive clarification
  • Can recommend /phx:intro for onboarding