Automate GitHub and Forgejo ticket handling from URL to review-ready implementation.
npx skills add https://github.com/SnowboardTechie/dotfiles --skill issue-work
Please help me install this Agent Skill. Skill: issue-work Source: https://github.com/SnowboardTechie/dotfiles/tree/main/dot-claude/skills/issue-work Command: npx skills add https://github.com/SnowboardTechie/dotfiles --skill issue-work
End-to-end ticket handling and execution pipeline—from intake and planning to implementation and self-review—driven by a GitHub/Forgejo ticket URL, a shorthand like owner/repo#N, or pasted ticket text, enabling reproducible, ticket-backed work.
Paste a ticket URL (or shorthand owner/repo#N) to start the intake workflow
High-intent search queries and answers about installing and using this skill.
Automating ticket workflow involves parsing a GitHub or Forgejo URL to generate an implementation plan, execute code changes, run tests, and prepare the output for human review. This Skill coordinates intake, planning, implementation, and testing through dedicated per-ticket workspaces.
Yes, you can use a shorthand like owner/repo#N to start the ticket planning workflow. The system parses this shorthand to digest the ticket text, generate an implementation plan, and spawn exploration agents within a per-ticket workspace.
Yes, automated ticket handling supports both GitHub and Forgejo repositories. It digests ticket URLs from either platform to create reproducible, ticket-backed workspaces that coordinate implementation, testing, and reviewer feedback.
Managing per-ticket state is handled by maintaining a plan-driven, gated workflow under a dedicated directory. This approach spawns exploration agents, tracks implementation progress, and coordinates parallel self-review before human handoff.
The ticket implementation process handles self-review by running parallel review agents alongside testing. It coordinates dedicated agents to evaluate the implementation against the plan before handing off the workspace for human review.
No, you do not need pasted ticket text if you have a ticket URL or a repository shorthand. The workflow accepts URLs, shorthands like owner/repo#N, or pasted text to start the intake and planning process for the implementation pipeline.
bostonaholicDecompose feature requests or issue URLs into QRSPI planning artifacts.
atxinskyExecute plan files in sequential batches with per-batch verification and human feedback between runs.
vaayneCoordinate plan-first development workflows with gate-based reviews and handoffs.
OgenticAIOrchestrate Linear ticket workflows with parallel processing, approvals, and tracking.
