work-issue
Start working on a GitHub issue. Fetches the issue details, creates a properly named branch, reads project context from chalk.json, and sets up a todo list for implementation.
Workflow
-
Fetch issue details — Use
gh issue view <number> --json title,body,labels,assignees,milestoneto get the full issue context. -
Read project context — If
.chalk/chalk.jsonexists, read it to understand:sourceLayout— where to create/modify filesroutes— which pages might be affectedproject.framework— framework-specific patterns to followdev.command— how to run the project for testing
-
Create a branch — Name it based on the issue:
- Feature:
feat/<issue-number>-<short-description> - Bug fix:
fix/<issue-number>-<short-description> - Chore:
chore/<issue-number>-<short-description> - Derive the type from issue labels (
bug→ fix,enhancement→ feat, default → feat) - Keep the description to 3-5 kebab-case words from the issue title
- Feature:
More from generaljerel/chalk-skills
python-clean-architecture
Clean architecture patterns for Python services — service layer, repository pattern, domain models, dependency injection, error hierarchy, and testing strategy
24create-handoff
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
16create-review
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any reviewer agent. Use after creating a handoff or when ready to get an AI code review.
15fix-findings
Fix findings from the active review session — reads reviewer findings files, applies fixes by priority, and updates the resolution log. Use after pasting reviewer output into findings files.
15fix-review
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
15review-changes
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
13