ijfw-agents-md
Maintain canonical AGENTS.md (open spec). Trigger: 'agents.md', 'update AGENTS.md', or auto-fired by ijfw-team after agent…
@ferroxlabsInstall SkillDevelopment
Skill
/ijfw-doctor
Diagnose IJFW integration health per platform. Trigger: 'doctor', 'check setup', /doctor
Claude Code
$ npx -y skills add FerroxLabs/ijfw --skill ijfw-doctor --agent claude-code
Codex
$ npx skills add FerroxLabs/ijfw --skill ijfw-doctor -a codex -y
Cursor
$ npx skills add FerroxLabs/ijfw --skill ijfw-doctor -a cursor -y
Gemini CLI
$ npx skills add FerroxLabs/ijfw --skill ijfw-doctor -a gemini-cli -y
GitHub Copilot
$ npx skills add FerroxLabs/ijfw --skill ijfw-doctor -a github-copilot -y
OpenCode
$ npx skills add FerroxLabs/ijfw --skill ijfw-doctor -a opencode -y
Windsurf
$ npx skills add FerroxLabs/ijfw --skill ijfw-doctor -a windsurf -y
SKILL.md
ijfw-doctor.SKILL.mdname: ijfw-doctor
description: "Diagnose IJFW integration health per platform. Trigger: 'doctor', 'check setup', /doctor"
IJFW Doctor
Run each check silently, then emit a single positive-framed report. Never say "failed", "error", or "not found" -- reframe every finding as an action or a ready state.
Checks (run in order)
1. MCP Server
Call `ijfw_metrics`. If it responds: "Memory server active". If unreachable: "Memory server ready to connect -- run `claude mcp add ijfw-memory node /path/to/mcp-server/src/index.js`".
2. Memory Directory
Check `.ijfw/memory/` exists and is writable (`test -w .ijfw/memory`). If writable: "Memory directory writable". If missing: "Memory directory ready to create -- first memory write will initialize it".
3. Hooks
Check for hook scripts in the platform's hooks directory (e.g. `~/.claude/hooks/` for Claude, `.codex/hooks/` for Codex). If scripts exist and are executable: "Hooks registered and live". If missing: "Hooks standing by -- re-run install.sh to register".
4. Platform Integration Depth
Report which features are active based on what's detected:
- MCP connected = deep integration
- Hooks present = prompt sharpener active
- Memory populated = context carry-over active
- Config present = custom rules loaded
5. Node.js Version
Run `node --version`. If 18+: "Runtime ready (Node <version>)". If missing or older: "Node.js 18+ needed -- install from https://nodejs.org".
Format
5-line list, one line per check, all positive. End with:
> `All systems active -- IJFW running at full depth.`
Or if any items need action:
> `IJFW active -- <N> of 5 systems at full depth. Steps above complete the setup.`
Under 20 lines total. No negatives.
Read more
name: ijfw-doctor description: "Diagnose IJFW integration health per platform. Trigger: 'doctor', 'check setup', /doctor"
IJFW Doctor
Run each check silently, then emit a single positive-framed report. Never say "failed", "error", or "not found" -- reframe every finding as an action or a ready state.
Checks (run in order)
1. MCP Server
Call `ijfw_metrics`. If it responds: "Memory server active". If unreachable: "Memory server ready to connect -- run `claude mcp add ijfw-memory node /path/to/mcp-server/src/index.js`".
2. Memory Directory
Check `.ijfw/memory/` exists and is writable (`test -w .ijfw/memory`). If writable: "Memory directory writable". If missing: "Memory directory ready to create -- first memory write will initialize it".
3. Hooks
Check for hook scripts in the platform's hooks directory (e.g. `~/.claude/hooks/` for Claude, `.codex/hooks/` for Codex). If scripts exist and are executable: "Hooks registered and live". If missing: "Hooks standing by -- re-run install.sh to register".
4. Platform Integration Depth
Report which features are active based on what's detected:
- MCP connected = deep integration
- Hooks present = prompt sharpener active
- Memory populated = context carry-over active
- Config present = custom rules loaded
5. Node.js Version
Run `node --version`. If 18+: "Runtime ready (Node <version>)". If missing or older: "Node.js 18+ needed -- install from https://nodejs.org".
Format
5-line list, one line per check, all positive. End with:
> `All systems active -- IJFW running at full depth.`
Or if any items need action:
> `IJFW active -- <N> of 5 systems at full depth. Steps above complete the setup.`
Under 20 lines total. No negatives.
Stats
215
Stars
44
Forks
Active
Maintenance
JavaScript
Language
MIT
License
Last commit
Created
Ships withijfw
IJFW — It Just F*cking Works. Ferrox Labs' local-first infrastructure for AI coding agents: shared memory, smart routing, multi-AI cross-audits, disciplined workflow.
21436 skills37 agents1 MCP
Stars on GitHub
Momentum
- stars in total
- 214
Other skills on ijfw.
@ferroxlabsInstall Skillijfw-auto-memorize
Session-end auto-extraction of lessons, errors, fixes, and user feedback into structured memory. Fires at session end. Requires…
@ferroxlabsInstall Skillijfw-commit
Terse conventional commits. Trigger: commit, git commit, /ijfw-commit
@ferroxlabsInstall Skillijfw-complete-mileston…
Use when a milestone is shipping and you need to archive its artifacts, generate a summary, and seed the next milestone. Trigger:…
@ferroxlabsInstall Skillijfw-compress
Compress memory/context files into terse form. Trigger: /compress, compress file
@ferroxlabsInstall Skillijfw-compute
Use when the user says: 'compute', 'crunch this', 'analyze logs', 'aggregate the data', 'run a script', 'dedupe', 'count by',…
@ferroxlabsInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about ijfw-doctor.
- Which coding agents can use ijfw-doctor?
- ijfw-doctor installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.