Skill
ijfw-agents-md
Maintain canonical AGENTS.md (open spec). Trigger: 'agents.md', 'update AGENTS.md', or auto-fired by ijfw-team after agent generation.
@ferroxlabsView SkillDevelopment
Skill
/ijfw-preflight
Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.
Install
$ npx -y skills add FerroxLabs/ijfw --skill ijfw-preflight --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ijfw-preflight
Context preview
The summary Claude sees to decide when to auto-load this skill.
Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.
SKILL.md
ijfw-preflight.SKILL.mdname: ijfw-preflight
description: "Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'."
IJFW Preflight
Runs 11 deterministic quality gates locally. Ordered fast-to-slow, fail-fast on blockers. Returns exit 0 on clean, exit 1 on findings.
Usage
ijfw preflight
What it checks
1. shellcheck -- shell script correctness 2. oxlint -- fast JS/TS linting 3. eslint-security -- high-signal JS security rules 4. psscriptanalyzer -- PowerShell scripts, with static fallback when pwsh is absent 5. publint -- package.json publish hygiene 6. gitleaks -- secret / credential scan 7. audit-ci -- npm dependency vulnerability check 8. knip -- dead code and unused exports 9. license-check -- dependency license compatibility 10. pack-smoke -- `npm pack` roundtrip + `ijfw --help` assert 11. upgrade-smoke -- upgrade from floor version, assert settings key survives
Behavior
- Each gate degrades gracefully to "skipped: tool not installed" when its CLI is absent (except blockers, which print actionable install hints).
- All output uses positive framing. No "failed" headers -- findings are reported as "surfaced N points".
- Runs under 90s on M-series laptop with warm caches.
- Pinned tool versions tracked in `.ijfw/preflight-versions.json`.
When to run
- Before every `git tag` / release.
- After any change to shell scripts, package.json, or dependency list.
- In CI (`.github/workflows/ci.yml` runs `ijfw preflight` on every push).
Read more
name: ijfw-preflight description: "Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'."
IJFW Preflight
Runs 11 deterministic quality gates locally. Ordered fast-to-slow, fail-fast on blockers. Returns exit 0 on clean, exit 1 on findings.
Usage
ijfw preflight
What it checks
1. shellcheck -- shell script correctness 2. oxlint -- fast JS/TS linting 3. eslint-security -- high-signal JS security rules 4. psscriptanalyzer -- PowerShell scripts, with static fallback when pwsh is absent 5. publint -- package.json publish hygiene 6. gitleaks -- secret / credential scan 7. audit-ci -- npm dependency vulnerability check 8. knip -- dead code and unused exports 9. license-check -- dependency license compatibility 10. pack-smoke -- `npm pack` roundtrip + `ijfw --help` assert 11. upgrade-smoke -- upgrade from floor version, assert settings key survives
Behavior
- Each gate degrades gracefully to "skipped: tool not installed" when its CLI is absent (except blockers, which print actionable install hints).
- All output uses positive framing. No "failed" headers -- findings are reported as "surfaced N points".
- Runs under 90s on M-series laptop with warm caches.
- Pinned tool versions tracked in `.ijfw/preflight-versions.json`.
When to run
- Before every `git tag` / release.
- After any change to shell scripts, package.json, or dependency list.
- In CI (`.github/workflows/ci.yml` runs `ijfw preflight` on every push).
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.
Get the whole plugin
Stats
210
Stars
40
Forks
Active
Maintenance
JavaScript
Language
MIT
License
1d ago
Last commit
5mo ago
Created
Repo: FerroxLabs/ijfw
Other skills on ijfw.
@ferroxlabsView SkillSkill
ijfw-auto-memorize
Session-end auto-extraction of lessons, errors, fixes, and user feedback into structured memory. Fires at session end. Requires consent on first run.
@ferroxlabsView SkillSkill
ijfw-commit
Terse conventional commits. Trigger: commit, git commit, /ijfw-commit
@ferroxlabsView SkillSkill
ijfw-complete-mileston…
Use when a milestone is shipping and you need to archive its artifacts, generate a summary, and seed the next milestone. Trigger: 'milestone complete', 'ship…
@ferroxlabsView SkillSkill
ijfw-compress
Compress memory/context files into terse form. Trigger: /compress, compress file
@ferroxlabsView SkillSkill
ijfw-compute
Use when the user says: 'compute', 'crunch this', 'analyze logs', 'aggregate the data', 'run a script', 'dedupe', 'count by', 'top N', or any data-shaping ask.…
@ferroxlabsView Skill