Skip to content
Back to search

forge

A collection of agent skills for structured, GitHub-centric development.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/mgratzer/forge with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/mgratzer/forge'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mgratzer--forge/badge.svg)](/listings/mgratzer--forge)

HTML

<a href="/listings/mgratzer--forge"><img src="/api/listings/mgratzer--forge/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install forge one way per machine:

# Claude Code: the skills plus the lens above
/plugin install forge --marketplace mgratzer/forge
# any other agent that reads Agent Skills
npx skills add mgratzer/forge

Then, in your project:

/forge-setup-project       # once per repo: AGENTS.md and the docs agents work from
/forge-ship 42             # implement Issue #42, review it in fresh context, open the PR
/forge-ship --guard 42     # and keep going: CI, review feedback, then a risk verdict

With the plugin, the commands are namespaced (`/forge:forge-ship`), and `/forge demo` replays a guarded run in the lens without touching GitHub.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 6 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "forge",
  3. "description": "forge: skills for a structured development workflow",
  4. "owner": { "name": "Martin Gratzer" },
  5. "plugins": [{ "name": "forge", "source": "./", "description": "forge skills and the forge lens" }]
  6. }
README.md · README · 109 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <img src="docs/images/icon-256.png" width="128" height="128" alt="forge icon: a pixel-art anvil with a glowing bar inside an ember progress ring">
  3. </p>
  4. <p align="center">
  5. <strong>Agent skills for structured development with pluggable issue tracking.</strong><br>
  6. One workflow. Ten skills. From idea to merged code.
  7. </p>
  8. <p align="center">
  9. <a href="#quick-start">Quick start</a> &middot;
  10. <a href="#how-it-works">How it works</a> &middot;
  11. <a href="#skills">Skills</a> &middot;
  12. <a href="docs/lens.md">Lens</a> &middot;
  13. <a href="docs/architecture.md">Architecture</a> &middot;
  14. <a href="#contributing">Contributing</a>
  15. </p>
  16. ---
  17. A forge is where raw material meets intention. You bring the codebase; these skills shape the workflow from issue to implementation to review.
  18. ---
  19. <p align="center">
  20. <img src="docs/images/lens.png" width="480" alt="The forge lens beside a Claude Code session: a guarded ship run with its current state, the next command, the pipeline, the PR's CI, review findings, the risk verdict and a timeline">
  21. </p>
  22. ## Quick Start
  23. Install forge one way per machine:
  24. ```
  25. # Claude Code: the skills plus the lens above
  26. /plugin install forge --marketplace mgratzer/forge
  27. ```
  28. ```bash
  29. # any other agent that reads Agent Skills
  30. npx skills add mgratzer/forge
  31. ```
  32. Then, in your project:
  33. ```
  34. /forge-setup-project # once per repo: AGENTS.md and the docs agents work from
  35. /forge-ship 42 # implement Issue #42, review it in fresh context, open the PR
  36. /forge-ship --guard 42 # and keep going: CI, review feedback, then a risk verdict
  37. ```
  38. With the plugin, the commands are namespaced (`/forge:forge-ship`), and `/forge demo` replays a guarded run in the lens without touching GitHub.
  39. ## How It Works
  40. ```
  41. forge-setup-project → [forge-shape →] forge-create-issue → forge-implement → forge-reflect → forge-address-pr-feedback → forge-guard → forge-land
  42. ╰──── forge-ship ────╯╰────────── forge-ship --guard ───────────╯
  43. ```
  44. **Ship** implements a change from an Issue, a plan file or a description: it researches the codebase, works in vertical phases with tests, runs the app on the changed path when the project says how, and opens a PR. A fresh-context reviewer, not the session that wrote the code, reviews the diff before you see it.
  45. **Guard** drives the open PR to review-ready without anyone watching: a simplification pass, a security pass when the diff calls for one, CI, the peer reviewer, and feedback in bounded rounds. It never merges.
  46. **Land** judges a green PR's risk on its head commit and writes the verdict into the PR. Low risk means you can merge without reading the diff; anything else comes with a list of where to look. It merges by itself only when the project opts in.
  47. Issues live wherever you keep them: GitHub, a markdown `plan/` folder in the repo, or a tracker you declare in `AGENTS.md`.
  48. ## Skills
  49. | Skill | Command | Purpose |
  50. |-------|---------|---------|
  51. | Setup Project | `/forge-setup-project` | Set up or audit a project's context for agentic engineering |
  52. | Shape | `/forge-shape` | Shape a vague idea into a clear plan, one question at a time, or one board at a time when the decision is visual |
  53. | Create Issue | `/forge-create-issue` | Plan and create Issues (GitHub, markdown, or another provider) |
  54. | Implement | `/forge-implement <input>` | Implement from an Issue, plan file, or description, and open the PR |
  55. | Reflect | `/forge-reflect` | Self-review changes: a PR, a branch, or uncommitted work |
  56. | Address PR Feedback | `/forge-address-pr-feedback` | Address unresolved PR feedback |
  57. | **Ship** | **`/forge-ship <input>`** | **Implement and review in one go; `--guard` continues through guard and land** |
  58. | Guard | `/forge-guard [pr]` | Drive an open PR to review-ready; never merges |
  59. | Land | `/forge-land [pr]` | Judge a green PR's risk: merge-ready, or review-ready with where to look |
  60. | Survey | `/forge-survey [paths]` | Review the codebase's design, record findings in `docs/surveys/`, and name the check that let each through |
  61. Every skill takes optional trailing guidance: `/forge-ship 42 -- keep the diff minimal`.
  62. ## The Lens
  63. The Claude Code plugin adds the lens: a pane beside the session that follows a forge run, with its current state, the command that most likely comes next, the PR's CI and review state, review findings, and the risk verdict. `/forge` says where a run is and what to do next. The lens only reads what the skills already print, so the skills work the same without it. See [Lens](docs/lens.md).
  64. ## Install Details
  65. **Claude Code plugin.** `/plugin install forge --marketplace mgratzer/forge` brings the skills and the lens. The plugin tracks commits on `main`: update with `claude plugin update forge@forge`, or turn on auto-update for the marketplace under `/plugin`.
  66. **npx skills.** `npx skills add mgratzer/forge` detects your agents and installs the skills to each of them ([skills.sh](https://skills.sh)).
  67. **Manual.** Symlink the skills into your agent's skills directory:
  68. ```bash
  69. ln -s /path/to/forge/skills/forge-* <your-agent-skills-dir>/
  70. ```
  71. Each skill carries its own copy of the shared modules in `_shared/`, so nothing else needs installing. Use one channel per machine: with both the plugin and npx, Claude Code lists every skill twice, once as `/forge-ship` and once as `/forge:forge-ship`. `npx skills update -g` recreates the `~/.claude/skills` links when `~/.claude` exists, so removing them doesn't last while the npx install remains.
  72. ## Contributing
  73. [`AGENTS.md`](AGENTS.md) has the commands CI runs and an index of the docs. Exercise a skill change in a sandbox repository, not a real project ([Testing](docs/testing.md#exercise-a-skill-change)), and use conventional commits (`feat(skills): add a skill`).
  74. ## License
  75. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.