Ticket Workflow
The ticket workflow connects GitHub issues to your Claude sessions so you do not have to paste issue bodies around manually.
Automatic Ticket Linking
Section titled “Automatic Ticket Linking”If you mention #123 or paste a GitHub issue URL in a prompt, CodeForge can fetch the issue context and inject it before Claude responds.
That means prompts like these work well:
Work on #42Fix the bug described in #108Review https://github.com/org/repo/issues/55
Main Commands
Section titled “Main Commands”| Command | Use It For |
|---|---|
/ticket:new | Create a structured GitHub issue |
/ticket:work | Explore the codebase and produce an implementation plan |
/ticket:review-commit | Review work against the ticket before committing |
/ticket:create-pr | Create a PR and post review findings |
Recommended Flow
Section titled “Recommended Flow”- Create or reference a ticket.
- Run
/ticket:workto produce a technical plan. - Implement the change.
- Run
/ticket:review-commitbefore committing. - Run
/ticket:create-prto open the PR and attach review output.
Tickets vs Specs
Section titled “Tickets vs Specs”Tickets are best for business-facing work tracking. Specs are best for detailed technical planning and implementation contracts.
For complex work, using both together is often the strongest flow.