do-issues
Work on GitHub issues systematically with proper development workflow
Best use case
do-issues is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Work on GitHub issues systematically with proper development workflow
Teams using do-issues should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/do-issues/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How do-issues Compares
| Feature / Agent | do-issues | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Work on GitHub issues systematically with proper development workflow
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Work on GitHub issues systematically with proper development workflow: $ARGUMENTS
Follow these steps:
1. **Review available GitHub issues**:
- Use `gh issue list` to see all open issues
- Choose a small, manageable task to complete
- If $ARGUMENTS specifies an issue number, work on that specific issue
2. **Plan your approach**:
- Use `gh issue view` to get detailed issue information
- Understand the problem and requirements thoroughly
- Post your implementation plan as a comment on the issue using `gh issue comment`
3. **Create a development branch**:
- Create a new branch with descriptive name: `git checkout -b fix/issue-{number}-{description}`
- Ensure branch is based on the latest main branch
4. **Implement the solution**:
- Search the codebase for relevant files using appropriate tools
- Write robust, well-documented code following existing patterns
- Include comprehensive tests with good coverage
- Add debug logging where appropriate
- Follow the project's coding standards and conventions
5. **Verify your implementation**:
- Run all existing tests to ensure nothing breaks
- Run linting and type checking if available
- Test your specific changes thoroughly
- Ensure all tests pass before proceeding
6. **Create a pull request**:
- Commit your changes with a descriptive commit message
- Push the branch to GitHub
- Use `gh pr create` to open a pull request
- Reference the issue in the PR description (e.g., "Closes #123")
- Base the PR on the previous branch if working on sequential issues
7. **Keep the issue open** until the pull request is merged
Remember: Each PR should build incrementally on previous work when working on related issues.Related Skills
make-github-issues
Review codebase and create GitHub issues for identified problems
workflow
Guide through structured delivery workflow with plan, implement, validate phases
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
validate
Verify implementation against specifications
ui-ux-pro-max
UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, Astro, Nuxt, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
tui-style-guide
TUI style guide for consistent terminal interface design
token-usage
Show Claude Code token usage across sessions — daily, weekly, per-project, and per-session breakdowns. Parses {{HOME_TOOL_DIR}}/projects/**/*.jsonl for consumption data. Use when the user asks about token usage, costs, how many tokens were used, session statistics, or wants a usage report.
tmux-status
Show status of all tmux sessions including dev environments, spawned agents, and running processes
tmux-monitor
Monitor and report status of all tmux sessions including dev environments, spawned agents, and running processes. Uses tmuxwatch for enhanced visibility.
tmux-message
Reliable peer-to-peer message delivery to other Claude Code instances via tmux send-keys. Use as a fallback when claude-peers MCP send_message fails to surface in the receiver's inbox (delivered server-side but receiver never picks it up — observed behaviour). Also use when sending a directive to a known Claude Code TUI session by tmux session name or fuzzy hint, or when injecting a multi-line directive into a peer's prompt and submitting it. Trigger phrases — "claude-peers fallback", "tmux send-keys", "send to peer via tmux", "inject directive", "deliver to nanoclaw/hermes peer", "peer message". Tmux-only — won't reach peers running outside tmux.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
test-ainb
Run tests for the ainb (agents-in-a-box) Rust workspace via a 5-layer strategy — unit, insta snapshot, mock-plugin compositing, real-plugin spawn, vhs recording. Wraps cargo + insta + vhs into one CLI. Use when Stevie says "/test-ainb", "test ainb", "run ainb tests", "snapshot <component>", "regenerate vhs tapes", or any phrasing about validating ainb test layers. The skill autodetects which ainb-tui worktree the cwd sits in and dispatches to scripts/run.sh.