Opsmill Dev Test Driving Bugs
opsmill/infrahub
Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written.
Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry.
Install Foreman Debug
$ npx skills add VisionForge-OU/foreman --skill foreman-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install VisionForge-OU/foreman foreman-debug --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/VisionForge-OU/foreman.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/foreman/skills/foreman-debug .claude/skills/foreman-debug && 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 "foreman-debug" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-debug into .claude/skills/foreman-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-debug", 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/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-debugType 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 VisionForge-OU/foreman --skill foreman-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install VisionForge-OU/foreman foreman-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/foreman/skills/foreman-debug .agents/skills/foreman-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "foreman-debug" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-debug into .agents/skills/foreman-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-debug", 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 VisionForge-OU/foreman --skill foreman-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install VisionForge-OU/foreman foreman-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/foreman/skills/foreman-debug .cursor/skills/foreman-debug && 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 "foreman-debug" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-debug into .cursor/skills/foreman-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-debug", 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/VisionForge-OU/foreman.git --path src/foreman/skills/foreman-debug--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 VisionForge-OU/foreman --skill foreman-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install VisionForge-OU/foreman foreman-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/foreman/skills/foreman-debug .gemini/skills/foreman-debug && 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 "foreman-debug" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-debug into .gemini/skills/foreman-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-debug", 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 VisionForge-OU/foreman foreman-debugInstalls 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 VisionForge-OU/foreman --skill foreman-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/foreman/skills/foreman-debug .github/skills/foreman-debug && 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 "foreman-debug" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-debug into .github/skills/foreman-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-debug", 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 VisionForge-OU/foreman --skill foreman-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install VisionForge-OU/foreman foreman-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/foreman/skills/foreman-debug .opencode/skills/foreman-debug && 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 "foreman-debug" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-debug into .opencode/skills/foreman-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-debug", 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
foreman-debug- GitHub stars
- 444
- Token cost
- ~1.1k tokens
- SKILL.md length
- 600 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry.
- Works in 4 steps: Root cause → Pattern → Hypothesis → …
- Tasks that involve Root cause analysis
- SKILL.md covers The Iron Law, The four phases (complete each…, When 3+ fixes have failed and Red flags — stop and return to…
- Calls git
What it does
Foreman Debug is an agent skill from VisionForge-OU/foreman. Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry. Find the root cause before changing anything, fix at the source with a regression test, and never thrash on symptom patches. Used inside a foreman-tdd build session; emits no summary of its own.
Its SKILL.md is about 1.1k 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 Testing & QA, covering Root cause analysis, Debugging and Test-driven development. The repository describes itself as: A Boris-style agentic orchestrator TUI that supervises headless Claude Code agents through a gated software-delivery pipeline — pointed at any repository.
When your agent uses it
- Tasks that involve Root cause analysis
- Tasks that involve Debugging
- Tasks that involve Test-driven development
Example prompts
- “/foreman-debug”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Root cause
- Pattern
- Hypothesis
- Fix at the source
What it can do on your machine
Read from SKILL.md and the folder at commit 92d7f79. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Foreman Debug loads about 1.1k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 600 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 600 words (~1,060 tokens).
“(Adapted from obra/superpowers systematic-debugging (MIT) — see NOTICE. Made headless: removed the "discuss with your human partner" hand-offs — under Foreman there is no live human, so a genuine architectural dead end becomes a FOREMAN-SUMMARY escalate from the surrounding foreman-tdd…”
- name
- foreman-debug
- foreman_skill_version
- 1
Files
Just SKILL.md in src/foreman/skills/foreman-debug of VisionForge-OU/foreman.
Open the folder on GitHubat commit 92d7f79
Compare with similar skills
Foreman Debug 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 |
|---|---|---|---|---|---|---|
| Foreman Debug this skillVisionForge-OU/foreman | 444 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Opsmill Dev Test Driving Bugsopsmill/infrahub | 529 | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Systematic Debuggingforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Verification Before Completionforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Triage Issuesoftspark/ai-toolkit | 179 | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| Nw BugfixnWave-ai/nWave | 617 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Systematic Debugging
foryourhealth111-pixel/Vibe-Skills
Root-cause route for actual bugs, failing tests, build errors, crashes, stack traces, and unexpected behavior.
Verification Before Completion
foryourhealth111-pixel/Vibe-Skills
Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.
Triage Issue
softspark/ai-toolkit
Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan.
Nw Bugfix
nWave-ai/nWave
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD
Compound Engineering Debug
EveryInc/compound-engineering-plugin
Finds the root cause of failing or slow behavior with a hypothesis-driven loop, then fixes it test-first if you choose, or hands back a diagnosis only.
More from VisionForge-OU/foreman
All 8 skills in this repoForeman Grill Docs
VisionForge-OU/foreman
Headless grilling pass that challenges an approved implementation plan against the existing codebase and domain model, then writes an ADR draft and a PRD draft into the Foreman feature directory.
Foreman To Issues
VisionForge-OU/foreman
Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory.
Foreman Verify
VisionForge-OU/foreman
Headless self-verification gate a Foreman worker runs before it claims an issue is done.
Foreman TDD
VisionForge-OU/foreman
Stack-agnostic test-driven development loop for a single Foreman issue.
Foreman Plan
VisionForge-OU/foreman
Headless implementation-plan authoring for the Foreman planning stage.
Foreman To Prd
VisionForge-OU/foreman
PRD template and authoring rules for Foreman. An agent skill from VisionForge-OU/foreman.
Related
Categories
Questions about Foreman Debug
What does Foreman Debug do?
Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry. Foreman Debug is an agent skill from VisionForge-OU/foreman. Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry.
When should I use Foreman Debug?
Foreman Debug fits situations like: tasks that involve Root cause analysis; tasks that involve Debugging; tasks that involve Test-driven development.
How do I install Foreman Debug in Claude Code?
Run `npx skills add VisionForge-OU/foreman --skill foreman-debug -a claude-code`. Or copy the skill folder (src/foreman/skills/foreman-debug in VisionForge-OU/foreman) into .claude/skills/foreman-debug in your project. Claude Code loads it when a task matches its description.
How do I install Foreman Debug in Codex?
Run `npx skills add VisionForge-OU/foreman --skill foreman-debug -a codex`. Or copy the skill folder (src/foreman/skills/foreman-debug in VisionForge-OU/foreman) into .agents/skills/foreman-debug in your project. Codex loads it when a task matches its description.
Can I use Foreman Debug 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 VisionForge-OU/foreman --skill foreman-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/foreman-debug, .gemini/skills/foreman-debug, .github/skills/foreman-debug and .opencode/skills/foreman-debug in your project.
What does Foreman Debug need to run?
Going by SKILL.md and its folder, Foreman Debug needs the command-line tools its instructions call (git).
Does Foreman Debug access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Foreman Debug 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 Foreman Debug use?
Foreman Debug has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Foreman Debug use?
About 1.1k tokens (SKILL.md is roughly 4.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 Foreman Debug?
Skills that share tags, products or a category with Foreman Debug: Opsmill Dev Test Driving Bugs (opsmill/infrahub, 529 stars), Systematic Debugging (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), Verification Before Completion (foryourhealth111-pixel/Vibe-Skills, 3.6k stars) and Triage Issue (softspark/ai-toolkit, 179 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Foreman Debug?
VisionForge-OU (a GitHub organization) maintains it in VisionForge-OU/foreman, which has 444 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on June 29, 2026.
Source: VisionForge-OU/foreman on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.