Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Root-cause analysis with hypothesis tracking. An agent skill from FerroxLabs/ijfw.
Install Ijfw Debug
$ npx skills add FerroxLabs/ijfw --skill ijfw-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FerroxLabs/ijfw ijfw-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/FerroxLabs/ijfw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/codex/skills/ijfw-debug .claude/skills/ijfw-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 "ijfw-debug" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/codex/skills/ijfw-debug into .claude/skills/ijfw-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-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/FerroxLabs/ijfw/tree/main/codex/skills/ijfw-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 FerroxLabs/ijfw --skill ijfw-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FerroxLabs/ijfw ijfw-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/codex/skills/ijfw-debug .agents/skills/ijfw-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 "ijfw-debug" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/codex/skills/ijfw-debug into .agents/skills/ijfw-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-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 FerroxLabs/ijfw --skill ijfw-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FerroxLabs/ijfw ijfw-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/codex/skills/ijfw-debug .cursor/skills/ijfw-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 "ijfw-debug" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/codex/skills/ijfw-debug into .cursor/skills/ijfw-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-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/FerroxLabs/ijfw.git --path codex/skills/ijfw-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 FerroxLabs/ijfw --skill ijfw-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FerroxLabs/ijfw ijfw-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/codex/skills/ijfw-debug .gemini/skills/ijfw-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 "ijfw-debug" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/codex/skills/ijfw-debug into .gemini/skills/ijfw-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-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 FerroxLabs/ijfw ijfw-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 FerroxLabs/ijfw --skill ijfw-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .github/skills && cp -r skills-src/codex/skills/ijfw-debug .github/skills/ijfw-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 "ijfw-debug" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/codex/skills/ijfw-debug into .github/skills/ijfw-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-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 FerroxLabs/ijfw --skill ijfw-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 FerroxLabs/ijfw ijfw-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/codex/skills/ijfw-debug .opencode/skills/ijfw-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 "ijfw-debug" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/codex/skills/ijfw-debug into .opencode/skills/ijfw-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-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
ijfw-debug- GitHub stars
- 212
- Token cost
- ~578 tokens
- SKILL.md length
- 267 words
- Files
- 1
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- MIT
At a glance
Root-cause analysis with hypothesis tracking. An agent skill from FerroxLabs/ijfw.
- Works in 6 steps: Reproduce → Check recent changes → Isolate → …
- Tasks that involve Root cause analysis
- SKILL.md covers Step 1 -- Reproduce, Step 2 -- Check recent changes, Step 3 -- Isolate and Step 4 -- Hypothesize, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ijfw Debug is an agent skill from FerroxLabs/ijfw. Root-cause analysis with hypothesis tracking. Trigger: 'debug', 'broken', 'not working', 'fix this bug', /debug
Its SKILL.md is about 580 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 Root cause analysis. The repository describes itself as: IJFW — It Just Fcking Works. Ferrox Labs' local-first infrastructure for AI coding agents: shared memory, smart routing, multi-AI cross-audits, disciplined workflow. The licence is MIT.
When your agent uses it
- Tasks that involve Root cause analysis
Example prompts
- “broken”
- “not working”
- “fix this bug”
- “/ijfw-debug”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit eda62f3. 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
Ijfw Debug loads about 578 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 267 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 FerroxLabs/ijfw at commit eda62f3, republished under its MIT licence (© FerroxLabs). 267 words, ~578 tokens.
Download SKILL.mdSave it as
.claude/skills/ijfw-debug/SKILL.md (or your agent's skills folder).- name
- ijfw-debug
- description
- Root-cause analysis with hypothesis tracking. Trigger: 'debug', 'broken', 'not working', 'fix this bug', /debug
Step 1 -- Reproduce
State the failure in one line: what was expected vs. what happened. Confirm reproducible before proceeding. If intermittent, note conditions.
Step 2 -- Check recent changes
Call ijfw_memory_recall with the symptom. Scan .ijfw/memory/ for decisions or
changes from the past 7 days that touch the affected area.
If a recent change correlates with the regression, offer revert first:
Regression likely from <change> on <date>. Revert first? (y/n)
Step 3 -- Isolate
- Narrow to the smallest reproducing case (file, function, line range).
- Determine if failure is input-dependent, environment-dependent, or logic-dependent.
- Read only the specific lines relevant to the hypothesis. No full-file reads.
Step 4 -- Hypothesize
List hypotheses ranked by likelihood:
H1 -- <most likely cause> -- evidence: <why>
H2 -- <next candidate> -- evidence: <why>
H3 -- <edge case> -- evidence: <why>Confirm H1 before testing H2.
Step 5 -- Fix and Verify
Apply the minimal change that addresses the root cause.
Do not fix adjacent issues -- log them as follow-ups.
Run tests/linter after every fix.
Confirm the original symptom is gone and no adjacent regression introduced.
Store result: ijfw_memory_store: <what broke>, <root cause>, <fix applied>
Step 6 -- Two-strikes session reset
If two attempts at root-cause fixes both fail to clear the original symptom, stop. Do not try a third on the same hypothesis tree. Summarize in three lines: what you tried, what each attempt revealed, what you now believe is true. Then ask the user:
Two attempts didn't land it. Recommend resetting this session and starting fresh with: "<sharpened prompt>". Accumulated failed context degrades the next attempt; a fresh session with a tighter brief usually clears it on the first try.
Capture the summary in ijfw_memory_store so the next session inherits the lessons without inheriting the noise.
Output format
SYMPTOM: <one line>
ROOT CAUSE: <H1 confirmed or revised>
FIX: <what changed + file:line>
VERIFIED: yes / needs more testing
FOLLOW-UPS: <any adjacent issues deferred>© FerroxLabs, 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 codex/skills/ijfw-debug of FerroxLabs/ijfw.
Open the folder on GitHubat commit eda62f3
Compare with similar skills
Ijfw 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 |
|---|---|---|---|---|---|---|
| Ijfw Debug this skillFerroxLabs/ijfw | 212 | — | ~578 | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Root Cause Debugginggarrytan/gstack | 136k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Graph-Based Bug Tracingtirth8205/code-review-graph | 32k | 1 repos | ~287 | Automated safety check: Pass | MIT |
Similar skills
- Official
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
Graph-Based Bug Tracing
tirth8205/code-review-graph
Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.
Om Auto Fix Issue
go-musicfox/go-musicfox
Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain…
More from FerroxLabs/ijfw
All 38 skills in this repoIjfw Agents Md
FerroxLabs/ijfw
Maintain canonical AGENTS.md (open spec). An agent skill from FerroxLabs/ijfw.
Ijfw Design
FerroxLabs/ijfw
A skill your agent uses when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience'…
Ijfw Complete Milestone
FerroxLabs/ijfw
A skill your agent uses when a milestone is shipping and you need to archive its artifacts, generate a summary, and seed the next milestone.
Ijfw Critique
FerroxLabs/ijfw
Challenge decisions, surface counter-arguments, flag assumptions.
Ijfw Cross Audit
FerroxLabs/ijfw
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact.
Ijfw Milestone Summary
FerroxLabs/ijfw
A skill your agent uses when the user asks for a milestone summary, milestone recap, or to summarize a milestone -- or runs /ijfw-milestone-summary.
Related
Categories
Questions about Ijfw Debug
What does Ijfw Debug do?
Root-cause analysis with hypothesis tracking. An agent skill from FerroxLabs/ijfw. Ijfw Debug is an agent skill from FerroxLabs/ijfw. Root-cause analysis with hypothesis tracking.
When should I use Ijfw Debug?
Ijfw Debug fits situations like: tasks that involve Root cause analysis.
How do I install Ijfw Debug in Claude Code?
Run `npx skills add FerroxLabs/ijfw --skill ijfw-debug -a claude-code`. Or copy the skill folder (codex/skills/ijfw-debug in FerroxLabs/ijfw) into .claude/skills/ijfw-debug in your project. Claude Code loads it when a task matches its description.
How do I install Ijfw Debug in Codex?
Run `npx skills add FerroxLabs/ijfw --skill ijfw-debug -a codex`. Or copy the skill folder (codex/skills/ijfw-debug in FerroxLabs/ijfw) into .agents/skills/ijfw-debug in your project. Codex loads it when a task matches its description.
Can I use Ijfw 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 FerroxLabs/ijfw --skill ijfw-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/ijfw-debug, .gemini/skills/ijfw-debug, .github/skills/ijfw-debug and .opencode/skills/ijfw-debug in your project.
What does Ijfw Debug need to run?
SKILL.md names no scripts, command-line tools or credentials: Ijfw Debug is instructions for the agent only.
Does Ijfw Debug 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 Ijfw 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 Ijfw Debug use?
Ijfw Debug 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 Ijfw Debug use?
About 578 tokens (SKILL.md is roughly 2.3k 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 Ijfw Debug?
Skills that share tags, products or a category with Ijfw Debug: Code Design Rationale Investigator (cursor/plugins, 10k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars) and Root Cause Debugging (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ijfw Debug?
FerroxLabs (a GitHub user) maintains it in FerroxLabs/ijfw, which has 212 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 5, 2026.
Source: FerroxLabs/ijfw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.