Redirects legacy issue commands to the plan, task, or go skills based on arguments.
npx skills add https://github.com/vzakharov/vovazakharov.com --skill issue-vzakharov
Please help me install this Agent Skill. Skill: issue Source: https://github.com/vzakharov/vovazakharov.com/tree/main/.claude/skills/issue Command: npx skills add https://github.com/vzakharov/vovazakharov.com --skill issue-vzakharov
/issue command, but its work has been split across three separate skills, leaving operators unsure which one actually runs. This Skill resolves that ambiguity by forwarding the invocation to the correct successor instead of silently doing the wrong thing. ## Core Features & Use Cases - Argument-based routing: When the argument contains an issue number like #42, it loads and follows the plan skill, passing the argument through unchanged. - Safe stop on missing number: When no issue number is present, it names the task skill and stops rather than running a workflow that quietly drops the issue premise. - Backward compatibility: Preserves the behavior operators expect from muscle memory, since /issue ... #N historically invoked what is now the plan skill. - Use Case: An operator types /issue fix the login redirect #57 from an old runbook; the command forwards to the plan skill with the full argument, then notes that task and go accept the same input. ## Quick Start Invoke /issue followed by a description and an issue number such as #42 to have it forwarded to the plan skill.High-intent search queries and answers about installing and using this skill.
Invoke /issue with your description and an issue number like #42, and it forwards everything to the plan skill unchanged. Without a number, it names the task skill and stops so you can decide how to proceed.
It does not run anything. The skill names the task skill and stops, because the old name implied an issue was involved and silently dropping that premise would hide a mistake from the operator.
Plan is the default because it is what /issue with a number invoked before the split, so it matches what an operator typing the old name expects. The skill also notes that task and go accept the same argument.
No. Reading an issue is handled by the take-issue skill, which is only called by other skills, not invoked directly. The /issue command only decides between plan, task, and go.
Once you know which behavior you want, call plan, task, or go directly. The /issue name exists only for backward compatibility with handoff blocks and muscle memory, not as a permanent interface.
stillwater-scInspect GitHub issue data and repository code to identify and resolve problems.
ymkzExecute development tasks autonomously within code repositories.
agents-repoFetches GitHub issue context via gh CLI and emits a structured issue brief.
samwelmungaInvokes a named Jenga playbook by ID, skipping natural-language matching to run its skill chain.