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.
Work through bugs or reported issues one cause at a time — reproduce the reporter's own case, explain the root cause with annotated evidence and a diagram, lay out fix options, wait for "go", then…
Install Explain Then Fix
$ npx skills add jnsahaj/skills --skill explain-then-fix -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jnsahaj/skills explain-then-fix --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/jnsahaj/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/explain-then-fix .claude/skills/explain-then-fix && 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 "explain-then-fix" agent skill from https://github.com/jnsahaj/skills/tree/main/skills/explain-then-fix into .claude/skills/explain-then-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-then-fix", 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/jnsahaj/skills/tree/main/skills/explain-then-fixType 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 jnsahaj/skills --skill explain-then-fix -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jnsahaj/skills explain-then-fix --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnsahaj/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/explain-then-fix .agents/skills/explain-then-fix && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "explain-then-fix" agent skill from https://github.com/jnsahaj/skills/tree/main/skills/explain-then-fix into .agents/skills/explain-then-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-then-fix", 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 jnsahaj/skills --skill explain-then-fix -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jnsahaj/skills explain-then-fix --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnsahaj/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/explain-then-fix .cursor/skills/explain-then-fix && 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 "explain-then-fix" agent skill from https://github.com/jnsahaj/skills/tree/main/skills/explain-then-fix into .cursor/skills/explain-then-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-then-fix", 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/jnsahaj/skills.git --path skills/explain-then-fix--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 jnsahaj/skills --skill explain-then-fix -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jnsahaj/skills explain-then-fix --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnsahaj/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/explain-then-fix .gemini/skills/explain-then-fix && 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 "explain-then-fix" agent skill from https://github.com/jnsahaj/skills/tree/main/skills/explain-then-fix into .gemini/skills/explain-then-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-then-fix", 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 jnsahaj/skills explain-then-fixInstalls 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 jnsahaj/skills --skill explain-then-fix -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jnsahaj/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/explain-then-fix .github/skills/explain-then-fix && 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 "explain-then-fix" agent skill from https://github.com/jnsahaj/skills/tree/main/skills/explain-then-fix into .github/skills/explain-then-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-then-fix", 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 jnsahaj/skills --skill explain-then-fix -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jnsahaj/skills explain-then-fix --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jnsahaj/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/explain-then-fix .opencode/skills/explain-then-fix && 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 "explain-then-fix" agent skill from https://github.com/jnsahaj/skills/tree/main/skills/explain-then-fix into .opencode/skills/explain-then-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-then-fix", 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
explain-then-fix- GitHub stars
- 105
- Token cost
- ~527 tokens
- SKILL.md length
- 301 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- None found
At a glance
Work through bugs or reported issues one cause at a time — reproduce the reporter's own case, explain the root cause with annotated evidence and a diagram, lay out fix options, wait for "go", then…
- Works in 6 steps: Pick. One problem, or a few that look… → Reproduce. On the reporter's own case:… → Explain. In plain words, naming things… → …
- Tasks that involve Root cause analysis
- SKILL.md covers Steps and Rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Explain Then Fix is an agent skill from jnsahaj/skills. Work through bugs or reported issues one cause at a time — reproduce the reporter's own case, explain the root cause with annotated evidence and a diagram, lay out fix options, wait for "go", then fix and show before/after.
Its SKILL.md is about 530 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: Agent skills I use daily.
When your agent uses it
- Tasks that involve Root cause analysis
Example prompts
- “/explain-then-fix”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Pick. One problem, or a few that look like one cause. Say which, in one
- Reproduce. On the reporter's own case: their data, their environment,
- Explain. In plain words, naming things the way the reporter would,
- Discuss. Lay out the fix options, each with what it fixes, what it
- Fix, on "go". Implement it. Add the few tests that fail before and
- Next. Say what is left of the group, then propose the next group and
What it can do on your machine
Read from SKILL.md and the folder at commit 170b0b9. 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
Explain Then Fix loads about 527 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 301 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 301 words (~527 tokens).
“The user decides every fix. Nothing is changed, pushed, closed or published until they say so, and everything happens in this chat.”
- name
- explain-then-fix
- disable-model-invocation
- true
Files
Just SKILL.md in skills/explain-then-fix of jnsahaj/skills.
Open the folder on GitHubat commit 170b0b9
Compare with similar skills
Explain Then Fix 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 |
|---|---|---|---|---|---|---|
| Explain Then Fix this skilljnsahaj/skills | 105 | — | ~527 | Automated safety check: Pass | None | |
| Code Design Rationale Investigatorcursor/plugins | 11k | 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 | |
| Review PRapache/shardingsphere | 21k | — | ~6.4k | Automated safety check: Pass | Apache-2.0 |
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.
Review PR
apache/shardingsphere
Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.
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.
More from jnsahaj/skills
All 8 skills in this repoGa PR
jnsahaj/skills
Kick off follow-up work on an existing PR in a parallel tmux/agent session.
Prepare Branch Context
jnsahaj/skills
Analyze the current branch's diff from main and related PR to build context for followup requests.
Create Draft PR
jnsahaj/skills
Commit, push, and create a draft PR using the pr-description format, with UX flow context when relevant.
Ga
jnsahaj/skills
Kick off a new feature or fix in a parallel clone with Pi working autonomously.
Pit Of Success
jnsahaj/skills
Review or refactor code so the correct behavior is the default path; use when APIs, setters, hooks, helpers, or component props have footguns where a natural call bypasses required semantics.
UX Flow Plan
jnsahaj/skills
Create UX-first plans as flow trees, then attach concrete function names, files, and implementation anchors after the high-level flow is clear.
Related
Categories
Questions about Explain Then Fix
What does Explain Then Fix do?
Work through bugs or reported issues one cause at a time — reproduce the reporter's own case, explain the root cause with annotated evidence and a diagram, lay out fix options, wait for "go", then…. Explain Then Fix is an agent skill from jnsahaj/skills. Work through bugs or reported issues one cause at a time — reproduce the reporter's own case, explain the root cause with annotated evidence and a diagram, lay out fix options, wait for "go", then fix and show before/after.
When should I use Explain Then Fix?
Explain Then Fix fits situations like: tasks that involve Root cause analysis.
How do I install Explain Then Fix in Claude Code?
Run `npx skills add jnsahaj/skills --skill explain-then-fix -a claude-code`. Or copy the skill folder (skills/explain-then-fix in jnsahaj/skills) into .claude/skills/explain-then-fix in your project. Claude Code loads it when a task matches its description.
How do I install Explain Then Fix in Codex?
Run `npx skills add jnsahaj/skills --skill explain-then-fix -a codex`. Or copy the skill folder (skills/explain-then-fix in jnsahaj/skills) into .agents/skills/explain-then-fix in your project. Codex loads it when a task matches its description.
Can I use Explain Then Fix 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 jnsahaj/skills --skill explain-then-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/explain-then-fix, .gemini/skills/explain-then-fix, .github/skills/explain-then-fix and .opencode/skills/explain-then-fix in your project.
What does Explain Then Fix need to run?
SKILL.md names no scripts, command-line tools or credentials: Explain Then Fix is instructions for the agent only.
Does Explain Then Fix 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 Explain Then Fix 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 Explain Then Fix use?
No licence was found for Explain Then Fix or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Explain Then Fix use?
About 527 tokens (SKILL.md is roughly 2.1k 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 Explain Then Fix?
Skills that share tags, products or a category with Explain Then Fix: Code Design Rationale Investigator (cursor/plugins, 11k 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 Explain Then Fix?
jnsahaj (a GitHub user) maintains it in jnsahaj/skills, which has 105 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 5, 2026.
Source: jnsahaj/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.