Agent skill
issue
Use when user says "/issue", "create issue", "file issue", "report bug", "request feature", "update issue", "check off", "verify issue", "view issue", or needs to manage GitHub issues.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/issue-zeroae-zae-limiter-2
SKILL.md
Issue Skill
Create, update, and manage GitHub issues following ZeroAE conventions. Infer as much as possible from context; only ask when ambiguous.
Modes
| Mode | Trigger | Purpose |
|---|---|---|
| View | "view issue", "view #123", /issue view <number> |
Display full issue details (body, criteria, deps, comments) |
| Create | "create issue", "file issue", "new issue", "report bug", "request feature" | Create new issue |
| Update | "update issue", "add to issue", "update #123" | Modify existing issue |
| Progress | "check off", "mark complete", "done with", "finished" | Check checkboxes based on work done |
| Verify | /issue verify <number> [--all] [--dry-run] |
Validate unchecked criteria, prompt to check off |
| Ralph Loop | /issue ralph-loop <number> [--max-iterations <n>] |
Iteratively work until all criteria pass |
| Scan | /issue scan [--milestone <name>] [--fix] |
Flag subjective acceptance criteria |
Mode Detection
When this skill is invoked, arguments follow the skill name (e.g., /issue view 135 passes "view 135" as arguments).
IMPORTANT: Before doing anything else, identify the mode from the invocation arguments:
| Arguments | Mode | Instructions |
|---|---|---|
view <number> |
View | Read view.md |
ralph-loop <number> |
Ralph Loop | Read ralph-loop.md |
scan [--milestone <name>] |
Scan | Read scan.md |
verify <number> |
Verify | Read verify.md |
| update phrases ("update issue", "add to #123") | Update | Read update.md |
| progress phrases ("check off", "mark complete") | Progress | Read progress.md |
| (none) or create phrases | Create | Read create.md |
First action: Read the appropriate .md file for your detected mode, then follow those instructions exactly.
Supported Issue Types
GitHub supports 5 issue types. The title emoji can be any gitmoji:
| GitHub Type | Canonical Emoji | Alternative Emojis | Use For |
|---|---|---|---|
| Bug | 🐛 | 🔒 (security) | Defects, unexpected behavior |
| Feature | ✨ | ⚡ (perf), 💥 (breaking) | New functionality, enhancements |
| Task | 📋 | 📝 (docs), ✅ (test) | Documentation, testing, specific work items |
| Chore | 🔧 | ♻️ (refactor), ⬆️ (deps), 👷 (ci), 🔥 (remove) | Maintenance: refactor, deps, ci, cleanup |
| Epic | 🎯 | - | Major feature spanning multiple issues |
| Theme | 🎨 | - | Strategic initiative spanning epics |
See conventions.md for full gitmoji-to-type mapping.
Note: For release preparation, use
/pr release <version>to create a Release Prep PR.
Reference Files
- view.md - View issue mode
- create.md - Create issue mode
- update.md - Update issue mode
- progress.md - Progress tracking mode
- verify.md - Acceptance criteria verification mode
- ralph-loop.md - Ralph Loop mode (iterative issue resolution)
- scan.md - Scan mode (flag subjective acceptance criteria)
- templates.md - Issue body templates for each type
- conventions.md - Label taxonomy, title formatting, milestone rules
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?