Agent skills for structured, GitHub-centric development.
One workflow. Six skills. From issue to shipped code.
Architecture · Development · Guidelines · Testing · PR Workflow
A forge is where raw material meets intention. You bring the codebase — these skills shape the workflow from issue to implementation to review.
Forge skills follow the Agent Skills open standard and work with any compatible agent.
| Skill | Command | Purpose |
|---|---|---|
| Setup Project | /forge-setup-project |
Create CLAUDE.md, docs/, README, and other meta-structure |
| Create Issue | /forge-create-issue |
Collaboratively plan and create GitHub issues |
| Implement Issue | /forge-implement-issue <number> |
Implement a feature or fix from a GitHub issue |
| Reflect on PR | /forge-reflect-pr |
Self-review before requesting peer review |
| Address PR Feedback | /forge-address-pr-feedback |
Address unresolved PR review comments |
| Update Changelog | /forge-update-changelog |
Update CHANGELOG.md with user-facing changes |
The skills form a pipeline — each step feeds into the next:
forge-setup-project → forge-create-issue → forge-implement-issue → forge-reflect-pr → forge-address-pr-feedback → forge-update-changelog
Forge skills follow the Agent Skills open standard and work with any compatible agent.
Via npx skills — auto-detects your agents and installs to all of them:
npx skills add mgratzer/forgeManual — symlink into your agent's skills directory:
ln -s /path/to/forge/skills/forge-* <your-agent-skills-dir>/Check your agent's docs for the skills directory path (e.g. ~/.claude/skills/, ~/.agents/skills/).
| Document | Purpose |
|---|---|
| Architecture | Skill pipeline, file format, design decisions |
| Development | How to create and modify skills |
| Coding Guidelines | Skill authoring conventions and style rules |
| Testing | How to validate skills manually |
| PR Workflow | Commits, PRs, branch naming, review process |
- Read CLAUDE.md for project principles and conventions
- Follow docs/coding-guidelines.md for skill authoring rules
- Test your changes by invoking the skill on a real project
- Use conventional commits:
feat(skills): add new skill