tomevault-io Task: Work on Issue $ARGUMENTS
Pull the specified GitHub issue and start planning work to complete it.
Related skills: Use github skill patterns for CLI commands. Follow planning skill workflow for the planning phase.
Step 0: Parse arguments
$ARGUMENTS is the issue ref optionally followed by a note. The first token is the issue ref, everything after is a note providing additional context.
Example: /issue 123 focus on the api endpoint, ignore the frontend for now → issue ref: 123, note: focus on the api endpoint, ignore the frontend for now
If a note is present, treat it as guidance throughout planning and execution — it may narrow scope, set priorities, or provide context not in the issue itself.
Step 1: Parse the issue reference
Parse the issue ref to determine the repo and issue number:
| Format | Example | Meaning |
|---|---|---|
| Number only | 123 |
Current repo, issue 123 |
owner/repo#number |
foo/bar#123 |
Repo foo/bar, issue 123 |
repo#number |
bar#123 |
Current owner + repo bar, issue 123 |
To get the current repo's owner:
gh repo view --json owner -q '.owner.login'
Step 2: Fetch issue details
Use github skill patterns:
gh issue view <number> --repo <owner/repo>
Step 3: Understand the requirements
- Read the issue description and comments
- Identify acceptance criteria
- Note linked issues or PRs
Step 4: Start planning workflow
Follow the planning skill:
- Understand the work from the issue
- Explore the codebase for relevant files
- Draft implementation plan
- Exit plan mode for approval
Step 5: Execute (after plan approval)
Per planning skill workflow:
- Track this as the active issue
- Do the work
- Create PR that closes the issue
Converted and distributed by TomeVault — claim your Tome and manage your conversions.