Skip to content

README.md

Latest commit

 

History

History
91 lines (64 loc) · 3.77 KB

README.md

File metadata and controls

91 lines (64 loc) · 3.77 KB

Agent skills for structured development with pluggable issue tracking.
One workflow. Six 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.

Skill Command Purpose
Setup Project /forge-setup-project Set up or audit a project's context infrastructure for agentic engineering
Shape /forge-shape Shape a vague idea into a clear plan through one-at-a-time structured questioning
Create Issue /forge-create-issue Collaboratively plan and create Issues (GitHub, markdown, or other provider)
Implement /forge-implement <input> Implement from an Issue, plan file, or description
Reflect /forge-reflect Self-review changes (PR, branch, or uncommitted)
Address PR Feedback /forge-address-pr-feedback Address unresolved PR review comments
Ship /forge-ship <input> Implement + review in one invocation

Skills with structured primary input also accept optional trailing execution guidance using -- <additional context>.

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. For fresh-context review in Pi, pair with pi-interactive-subagents.

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-* <your-agent-skills-dir>/

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

Document Purpose
Context Shared vocabulary used across forge skills
Architecture Skill workflow, 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

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