Ijfw Debug

Root-cause analysis with hypothesis tracking. Trigger: 'debug', 'broken', 'not working', 'fix this bug', /debug

43 stars 17 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add FerroxLabs/wayland-core --skill ijfw-debug
Manual install
git clone --depth 1 https://github.com/FerroxLabs/wayland-core.git /tmp/wayland-core
mkdir -p ~/.claude/skills
cp -r /tmp/wayland-core/crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-debug ~/.claude/skills/ijfw-debug

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

## 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
Read the full skill on GitHub

Details

Skill name
ijfw-debug
Path
crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-debug/SKILL.md
License
Apache-2.0
Repo updated
3 November 2026

FAQ

What does the Ijfw Debug skill do?

Root-cause analysis with hypothesis tracking. Trigger: 'debug', 'broken', 'not working', 'fix this bug', /debug

How do I install the Ijfw Debug skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add FerroxLabs/wayland-core --skill ijfw-debug. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Ijfw Debug popular?

It lives in FerroxLabs/wayland-core, which has 43 GitHub stars and 17 forks.

Related skills

Ijfw Agents Md

43

FerroxLabs/wayland-core

Maintain canonical AGENTS.md (open spec). Trigger: 'agents.md', 'update AGENTS.md', or auto-fired by ijfw-team after agent generation.

AI, LLMs & Agents17

Ijfw Auto Memorize

43

FerroxLabs/wayland-core

Session-end auto-extraction of lessons, errors, fixes, and user feedback into structured memory. Fires at session end. Requires consent on first run.

Productivity & Notes17

Ijfw Commit

43

FerroxLabs/wayland-core

Terse conventional commits. Trigger: commit, git commit, /ijfw-commit

Git & Code Review17

Skill Developer Meta

48

harvard-lil/lawskills-hub

Always-on assistant for creating, reviewing, and testing pedagogical AI skills for the Legal Ed Skills Hub. Triggers on writing new skills, reviewing skill quality, evaluating skill pedagogy, testing skills against rubrics, defining evaluation criteria, or any task related to building and improving agent skills for legal education.

Software Development

Feature Lifecycle

40

tddworks/claude-skills

Full-lifecycle guide for implementing a feature end-to-end in a London-school DDD Swift/iOS codebase (or any layered Domain/Infrastructure/App project that uses protocol + concrete impl aggregates, narrow infrastructure ports, and Chicago-school state-based TDD). Use this skill whenever the user asks to **build**, **implement**, **add**, **ship**, or **develop** a feature — including vague asks like "let's add X", "build me Y", "implement Z", or "wire up the W flow". Strongly prefer this skill over jumping straight to code whenever a new domain concept is in play. Each lifecycle phase has its

Software Development

Skill Reviewer

48

harvard-lil/lawskills-hub

Reviews and evaluates an existing SKILL.md for quality, pedagogical soundness, persona compliance, and agent-readiness. Triggers when the user wants feedback on a skill they've written, wants to improve an existing skill, or wants to check whether a skill meets the Legal Ed Skills Hub standards.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.