mgratzer/forge

Agent skills for structured development with pluggable issue tracking. One workflow. Seven skills. From idea to review-ready code.

Context · 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.

---

Skills

Forge skills follow the Agent Skills open standard and work with any compatible agent.

All skills accept optional trailing execution guidance using -- .

Workflow

The skills form a simple workflow — each step feeds into the next:

forge-setup-project → [forge-shape →] forge-create-issue → forge-implement → forge-reflect → forge-address-pr-feedback
                                                                        ╰──── forge-ship ────╯

forge-ship composes implement + review into a single invocation; its review always delegates to a fresh-context reviewer (the session authored the diff), adding a second pass only when risk justifies it. Standalone forge-reflect keeps tiny diffs inline when the session didn’t author them. Scout and review work should use cheaper models when the runtime supports per-task model choice; otherwise they should inherit the parent session model cleanly.

Install

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/forge

Manual — symlink into your agent’s skills directory:

ln -s /path/to/forge/skills/forge-* /path/to/forge/skills/_shared /

Both forge-* skills and the _shared/ directory are required — skills reference shared modules via ../_shared/ paths. Check your agent’s docs for the correct skills directory path.

Project Guidance

• AGENTS.md is the canonical project guidance file
• CLAUDE.md is a compatibility symlink for tools that still look for that filename

Documentation

Contributors

• @denrase — configurable git workflow idea (#7)

Contributing

1. Read AGENTS.md for project principles and conventions
2. Follow docs/coding-guidelines.md for skill authoring rules
3. Test your changes by invoking the skill on a real project
4. Use conventional commits: feat(skills): add new skill