oliver-kriska/claude-elixir-phoenix / targets/codex/skills/phx-help
phx-help
VerifiedRecommend the right $elixir-phoenix:phx-* workflow. Use when choosing a plugin skill, not for Codex /help.
Plugin Help — Interactive Command Advisor
Helps users find the right command, skill, or agent for their situation.
Usage
$elixir-phoenix:phx-help # Analyze context, suggest commands
$elixir-phoenix:phx-help how do I debug this? # Route to $elixir-phoenix:phx-investigate
$elixir-phoenix:phx-help add a new feature # Route to $elixir-phoenix:phx-plan -> $elixir-phoenix: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):
- Check for existing plans: use Glob on
.claude/plans/*/plan.md— active work in progress? - Check git status: uncommitted changes? which files?
- Check for solution docs: use Glob on
.claude/solutions/**/*.md— prior knowledge?
Step 2: Classify Intent
Read references/tool-catalog.md for the full routing table.
Map the user's situation to one of these categories:
| Category | Signals | Primary Commands |
|---|---|---|
| Starting out | No plans, new to plugin | $elixir-phoenix:phx-intro |
| Ideation | "explore", "brainstorm", "not sure", "how to approach", "vague idea" | $elixir-phoenix:phx-brainstorm |
| New feature | "add", "build", "implement", multi-file | $elixir-phoenix:phx-plan → $elixir-phoenix:phx-work |
| Quick change | Single file, <50 lines, "fix typo" | $elixir-phoenix:phx-quick |
| Bug | Error, stack trace, "broken", "failing" | $elixir-phoenix:phx-investigate |
| Review | "check", "review", PR ready | $elixir-phoenix:phx-review |
| Performance | "slow", "N+1", "memory" | $elixir-phoenix:phx-perf, $elixir-phoenix:ecto-n1-check, $elixir-phoenix:lv-assigns |
| Research | "how to", "best practice", "evaluate lib" | $elixir-phoenix:phx-research |
| Resume work | Existing plan with unchecked tasks | $elixir-phoenix:phx-work --continue |
| Post-fix | "that worked", solved a hard bug | $elixir-phoenix:phx-compound |
| Full cycle | Large feature, new domain area | $elixir-phoenix:phx-full |
| Project health | "audit", "tech debt", "overall quality" | $elixir-phoenix:phx-audit, $elixir-phoenix:phx-techdebt |
| Dep update audit | "audit deps", "supply chain", "post-mix deps.update", "review mix.lock PR" | $elixir-phoenix:phx-deps-audit |
| Manual dep vetting | "vet this package", "approve dep", "trust ledger", "after $elixir-phoenix:phx-deps-audit findings" | $elixir-phoenix:phx-deps-vet |
| Deployment | "deploy", "release", "production" | $elixir-phoenix:phx-verify then deploy skill |
| Permissions | "too many prompts", "allow", "permission fatigue" | $elixir-phoenix: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
$elixir-phoenix:phx-helpanytime to get routing advice" - If they seem new: "Try
$elixir-phoenix:phx-introfor a full plugin walkthrough"
Iron Laws
- ONE recommendation — don't dump the full catalog, pick the best match
- MAX ONE clarifying question — don't interrogate, make your best guess
- Show exact syntax —
$elixir-phoenix:phx-plan Add user notificationsnot just "use the plan command" - Context over keywords — existing plans + git state matter more than word matching
- 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
$elixir-phoenix:phx-introfor onboarding
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |