work-on-issue

Automate GitHub issue implementation with worktrees, tests, and pull requests.

45|7|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/richkuo/rk-skills --skill work-on-issue-richkuo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-on-issue
Source: https://github.com/richkuo/rk-skills/tree/main/skills/work-on-issue
Command: npx skills add https://github.com/richkuo/rk-skills --skill work-on-issue-richkuo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of context-switching, branch management, and PR creation when implementing GitHub issues, ensuring that fixes are built, verified, and submitted according to repository standards without human intervention.

Core Features & Use Cases

  • Autonomous Workflow: Handles the entire lifecycle from issue validation and worktree isolation to implementation, testing, and PR submission.
  • Safety & Verification: Enforces strict guardrails, including regression testing and dependency integration, to ensure code quality and prevent regressions.
  • Use Case: When a developer identifies a bug or feature request, this skill can be triggered to automatically create a fresh worktree, implement the fix, verify it with tests, and open a pull request that closes the issue.

Quick Start

Invoke the work-on-issue skill by providing the GitHub issue number or URL to automatically implement the fix and open a pull request.

Frequently Asked Questions about work-on-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue implementation from start to finish?

Automating GitHub issue implementation involves managing isolated worktrees, verifying code changes, and submitting pull requests. This skill handles the entire lifecycle, from issue validation to automated PR submission, ensuring repository standards are met without manual intervention.

What is the best way to automate pull request creation and code verification?

Automating pull request creation requires enforcing strict guardrails like regression testing and dependency integration. This approach ensures deterministic code contributions by verifying changes in isolated worktrees before opening a pull request that closes the original issue.

Can I use git worktrees to isolate automated code changes for GitHub issues?

Yes, using git worktrees isolates automated code changes for GitHub issues. This skill creates a fresh worktree for each issue, implements the fix, runs tests to prevent regressions, and submits a convention-compliant pull request.

How do I ensure automated code changes pass repository invariants and regression tests?

To ensure automated code changes pass repository invariants and regression tests, strict guardrails must be enforced. This skill verifies code changes through automated testing and deterministic dependency integration before submitting any pull requests.

Do I need to manually manage branches when automating GitHub pull requests?

No, manual branch management is not needed when automating GitHub pull requests. This skill eliminates manual overhead by automatically managing isolated worktrees, implementing fixes, and submitting pull requests that adhere to repository invariants.