From forge
Use when about to assert that a build passed, tests passed, types are clean, or linting succeeded — before writing that claim. Requires real tool call evidence; blocks prose assertions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/forge:evidence-gateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**If you have not run the command in this response, you cannot say it passed.**
If you have not run the command in this response, you cannot say it passed.
"Build passed ✅" with no Bash call is a hallucination. Show the command, show the exit code, show the output snippet — or do not make the claim.
A claim is valid only when the same response contains a tool call that produced the result. Evidence requirements:
| Claim | Required evidence |
|---|---|
| "Build passed" | Bash call showing exit 0 + build output |
| "Tests passed" | Bash call with test runner output + pass count |
| "Types are clean" | Bash call with type checker output showing 0 errors |
| "Linting passed" | Bash call with linter output showing 0 violations |
| "Diagnostics clean" | ide-get_diagnostics call showing 0 errors |
Running build to confirm...
[Bash: npm run build]
→ exit 0, output: "Build complete in 3.2s"
Build passed ✅
The build should still pass since I only changed the validation logic.
Build passed ✅ ← BLOCKED — no tool call, no evidence
If you cannot run the verification command right now, write: "I have not verified this — run <command> to confirm."
npx claudepluginhub addeelnayyer/forge --plugin forgeProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.