Forge CLI Debug Workflow
tailcallhq/forgecode
Gives a systematic process for debugging the forge CLI: build in debug mode, check the latest help output, test with the non-interactive -p flag, and clone conversations before reproducing bugs.
Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix.
Install Regression Proof
$ npx skills add Neeeophytee/finding-unknowns-skills --skill regression-proof -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills regression-proof --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/regression-proof .claude/skills/regression-proof && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "regression-proof" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/regression-proof into .claude/skills/regression-proof/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regression-proof", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/regression-proofType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill regression-proof -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills regression-proof --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/regression-proof .agents/skills/regression-proof && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "regression-proof" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/regression-proof into .agents/skills/regression-proof/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regression-proof", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill regression-proof -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills regression-proof --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/regression-proof .cursor/skills/regression-proof && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "regression-proof" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/regression-proof into .cursor/skills/regression-proof/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regression-proof", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Neeeophytee/finding-unknowns-skills.git --path skills/regression-proof--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill regression-proof -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills regression-proof --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/regression-proof .gemini/skills/regression-proof && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "regression-proof" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/regression-proof into .gemini/skills/regression-proof/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regression-proof", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Neeeophytee/finding-unknowns-skills regression-proofInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Neeeophytee/finding-unknowns-skills --skill regression-proof -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/regression-proof .github/skills/regression-proof && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "regression-proof" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/regression-proof into .github/skills/regression-proof/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regression-proof", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Neeeophytee/finding-unknowns-skills --skill regression-proof -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills regression-proof --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/regression-proof .opencode/skills/regression-proof && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "regression-proof" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/regression-proof into .opencode/skills/regression-proof/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regression-proof", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
regression-proof- GitHub stars
- 343
- Token cost
- ~790 tokens
- SKILL.md length
- 420 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix.
- Works in 6 steps: Establish the reported failure, expected… → Add the smallest regression test that… → Trace the cause and make a scoped fix… → …
- Implementing a bug fix
- SKILL.md covers Steps and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Regression Proof is an agent skill from Neeeophytee/finding-unknowns-skills. Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix. Use when implementing a bug fix or checking whether a proposed fix actually addresses a reported failure. Not a general coverage audit or new-feature workflow.
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. The repository describes itself as: 14 installable skills for Claude Code, OpenAI Codex, and Hermes: find unknowns, clarify requirements, manage context, test assumptions, and verify bug fixes with regression… The licence is MIT.
When your agent uses it
- Implementing a bug fix
- Checking whether a proposed fix actually addresses a reported failure
Example prompts
- “/regression-proof”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Establish the reported failure, expected behavior, and authorized scope from the request, relevant code, and existing tests. Record the…
- Add the smallest regression test that exercises the real failing path and asserts the required outcome. Run it against the original…
- Trace the cause and make a scoped fix when implementation is authorized. For review-only requests, assess the proposed fix without…
- Run the same regression test against the fixed behavior. If the fix existed before the test, compare with the original implementation in…
- Check the neighboring behavior most likely to be affected. Where an incomplete fix could pass the reproducer, add a discriminating case…
- Finish with the cause, fix or review finding, commands and observed before/after outcomes, adjacent checks, and remaining uncertainty. If…
What it can do on your machine
Read from SKILL.md and the folder at commit ca5696a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Regression Proof loads about 790 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 420 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Neeeophytee/finding-unknowns-skills at commit ca5696a, republished under its MIT licence (© Neeeophytee). 420 words, ~790 tokens.
Download SKILL.mdSave it as
.claude/skills/regression-proof/SKILL.md (or your agent's skills folder).- name
- regression-proof
- description
- Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix. Use when implementing a bug fix or checking whether a proposed fix actually addresses a reported failure. Not a general coverage audit or new-feature workflow.
Regression proof
A passing test is evidence for a fix only if it can distinguish the broken behavior from the intended behavior.
Steps
- Establish the reported failure, expected behavior, and authorized scope from the request, relevant code, and existing tests. Record the starting state, including uncommitted changes. Run the relevant baseline and reproduce the bug before editing when possible; distinguish a product failure from a broken test environment.
- Add the smallest regression test that exercises the real failing path and asserts the required outcome. Run it against the original behavior and verify that it fails for the reported reason, not an import error, missing dependency, or unrelated failure. Reuse an existing test if it already demonstrates this.
- Trace the cause and make a scoped fix when implementation is authorized. For review-only requests, assess the proposed fix without silently changing production code. Preserve the evidence from the original failure.
- Run the same regression test against the fixed behavior. If the fix existed before the test, compare with the original implementation in an isolated copy or worktree that preserves the relevant starting state. Do not reset the user's working tree. If an equivalent comparison cannot be made, report that limitation rather than claiming a verified before/after result.
- Check the neighboring behavior most likely to be affected. Where an incomplete fix could pass the reproducer, add a discriminating case. Use reference comparisons, bounded randomized checks, or performance measurements only when the failure mechanism warrants them; record seeds and conditions needed to reproduce results.
- Finish with the cause, fix or review finding, commands and observed before/after outcomes, adjacent checks, and remaining uncertainty. If the bug cannot be reproduced or expected behavior is unresolved, say what evidence is missing and avoid a speculative fix. Stop once the scoped claim is supported and relevant checks pass.
Show full SKILL.md (114 more words)Show less
Guardrails
- Never weaken assertions, change expected behavior merely to make a test pass, or mock away the boundary responsible for the bug.
- Preserve existing tests and unrelated user changes. Keep comparison artifacts isolated; do not use destructive checkout or reset operations to recreate the original failure.
- A missing dependency or unavailable original version is a verification limitation, not proof of correctness. Keep pre-existing failures separate from regressions caused by the fix.
- Keep execution within the task's authorization. A local reproducer does not authorize production writes, external side effects, or an unrelated refactor.
- A regression test establishes the tested behavior, not the absence of all bugs. This skill does not change the host's reasoning-effort setting.
© Neeeophytee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/regression-proof of Neeeophytee/finding-unknowns-skills.
Open the folder on GitHubat commit ca5696a
Compare with similar skills
Regression Proof next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Regression Proof this skillNeeeophytee/finding-unknowns-skills | 343 | — | ~790 | Automated safety check: Pass | MIT | |
| Forge CLI Debug Workflowtailcallhq/forgecode | 7.6k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Issue Fixmono/SkiaSharp | 5.6k | — | ~5.1k | Automated safety check: Pass | MIT | |
| React Router Bug Fix Workflowremix-run/react-router | 57k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Runtime Debugvercel/next.js | 143k | 1 repos | ~618 | Automated safety check: Pass | MIT | |
| OpenROAD Bug FixerThe-OpenROAD-Project/OpenROAD | 3.2k | — | ~784 | Automated safety check: Pass | BSD-3-Clause |
Similar skills
Issue Fix
mono/SkiaSharp
Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.
React Router Bug Fix Workflow
remix-run/react-router
Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.
- Official
Runtime Debug
vercel/next.js
Debug and verification workflow for runtime-bundle and module-resolution regressions.
OpenROAD Bug Fixer
The-OpenROAD-Project/OpenROAD
Fixes an OpenROAD bug from a GitHub issue or error code: finds the root cause, implements the fix, adds a regression test and prepares a signed-off commit.
Extension Puppeteer Debugging
mengxi-ream/read-frog
Debug the built Read Frog extension in real Chrome. An agent skill from mengxi-ream/read-frog.
More from Neeeophytee/finding-unknowns-skills
All 14 skills in this repoAgent Interface Design
Neeeophytee/finding-unknowns-skills
Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples.
Assumption Test
Neeeophytee/finding-unknowns-skills
Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach.
Blindspot Pass
Neeeophytee/finding-unknowns-skills
Surface the user's unknown unknowns before work starts. An agent skill from Neeeophytee/finding-unknowns-skills.
Brainstorm Prototypes
Neeeophytee/finding-unknowns-skills
Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to.
Change Quiz
Neeeophytee/finding-unknowns-skills
After a working session, produce a report on what changed plus a quiz the user must pass before merging.
Context Audit
Neeeophytee/finding-unknowns-skills
Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list.
Related
Categories
Questions about Regression Proof
What does Regression Proof do?
Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix. Regression Proof is an agent skill from Neeeophytee/finding-unknowns-skills. Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix.
When should I use Regression Proof?
Regression Proof fits situations like: implementing a bug fix; checking whether a proposed fix actually addresses a reported failure.
How do I install Regression Proof in Claude Code?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill regression-proof -a claude-code`. Or copy the skill folder (skills/regression-proof in Neeeophytee/finding-unknowns-skills) into .claude/skills/regression-proof in your project. Claude Code loads it when a task matches its description.
How do I install Regression Proof in Codex?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill regression-proof -a codex`. Or copy the skill folder (skills/regression-proof in Neeeophytee/finding-unknowns-skills) into .agents/skills/regression-proof in your project. Codex loads it when a task matches its description.
Can I use Regression Proof in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Neeeophytee/finding-unknowns-skills --skill regression-proof -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/regression-proof, .gemini/skills/regression-proof, .github/skills/regression-proof and .opencode/skills/regression-proof in your project.
What does Regression Proof need to run?
SKILL.md names no scripts, command-line tools or credentials: Regression Proof is instructions for the agent only.
Does Regression Proof access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Regression Proof safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Regression Proof use?
Regression Proof is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Regression Proof use?
About 790 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Regression Proof?
Skills that share tags, products or a category with Regression Proof: Forge CLI Debug Workflow (tailcallhq/forgecode, 7.6k stars), Issue Fix (mono/SkiaSharp, 5.6k stars), React Router Bug Fix Workflow (remix-run/react-router, 57k stars) and Runtime Debug (vercel/next.js, 143k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Regression Proof?
Neeeophytee (a GitHub user) maintains it in Neeeophytee/finding-unknowns-skills, which has 343 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 28, 2026.
Source: Neeeophytee/finding-unknowns-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.