Agent skill

Ijfw Review

A skill your agent uses when the user asks for a review of any artifact -- code diff, PR, book chapter, campaign brief, landing-page copy, or design tokens.

MITAuto-check passedFrontend & Design

Install Ijfw Review

skills CLI

$ npx skills add FerroxLabs/ijfw --skill ijfw-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install FerroxLabs/ijfw ijfw-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/ijfw-review .claude/skills/ijfw-review && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "ijfw-review" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-review into .claude/skills/ijfw-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-review", 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

$skill-installer install https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-review

Type 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.

skills CLI

$ npx skills add FerroxLabs/ijfw --skill ijfw-review -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install FerroxLabs/ijfw ijfw-review --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude/skills/ijfw-review .agents/skills/ijfw-review && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ijfw-review" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-review into .agents/skills/ijfw-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-review", 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.

skills CLI

$ npx skills add FerroxLabs/ijfw --skill ijfw-review -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install FerroxLabs/ijfw ijfw-review --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude/skills/ijfw-review .cursor/skills/ijfw-review && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ijfw-review" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-review into .cursor/skills/ijfw-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-review", 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

$ gemini skills install https://github.com/FerroxLabs/ijfw.git --path claude/skills/ijfw-review

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add FerroxLabs/ijfw --skill ijfw-review -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install FerroxLabs/ijfw ijfw-review --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude/skills/ijfw-review .gemini/skills/ijfw-review && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "ijfw-review" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-review into .gemini/skills/ijfw-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-review", 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.

GitHub CLI

$ gh skill install FerroxLabs/ijfw ijfw-review

Installs 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).

skills CLI

$ npx skills add FerroxLabs/ijfw --skill ijfw-review -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude/skills/ijfw-review .github/skills/ijfw-review && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "ijfw-review" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-review into .github/skills/ijfw-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-review", 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.

skills CLI

$ npx skills add FerroxLabs/ijfw --skill ijfw-review -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install FerroxLabs/ijfw ijfw-review --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude/skills/ijfw-review .opencode/skills/ijfw-review && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ijfw-review" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-review into .opencode/skills/ijfw-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-review", 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-review
GitHub stars: 212
Token cost: ~1.2k tokens
SKILL.md length: 471 words
Files: 1
Skills in repo: 38
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when the user asks for a review of any artifact -- code diff, PR, book chapter, campaign brief, landing-page copy, or design tokens.

The user asks for a review of any artifact -- code diff
SKILL.md covers Severity vocabulary (all…, Domain checklists, Output rules and Artifact-write contract…, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Landing-page copy

What it does

Ijfw Review is an agent skill from FerroxLabs/ijfw. Use when the user asks for a review of any artifact -- code diff, PR, book chapter, campaign brief, landing-page copy, or design tokens. Trigger: review, code review, review this, PR review, review my X, review chapter, review brief, review page, /ijfw-review

Its SKILL.md is about 1.2k 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 Frontend & Design, covering Copywriting, Code review and Pull requests. 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

The user asks for a review of any artifact -- code diff
Landing-page copy

Example prompts

“/ijfw-review”

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 (its code samples are markdown and gate-result).
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 Review loads about 1.2k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 471 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~68
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

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). 471 words, ~1,243 tokens.

Download SKILL.mdSave it as .claude/skills/ijfw-review/SKILL.md (or your agent's skills folder).

name: ijfw-review
description: Use when the user asks for a review of any artifact -- code diff, PR, book chapter, campaign brief, landing-page copy, or design tokens. Trigger: review, code review, review this, PR review, review my X, review chapter, review brief, review page, /ijfw-review
since: 1.5.0

Domain-agnostic critique. One-line findings, severity-tagged, with a written REVIEW.md artifact.

Severity vocabulary (all domains)

BLOCK -- must-fix before ship. Bug, data loss, broken claim, factual error, WCAG violation, missing CTA.
FLAG -- should discuss. Risky choice, weak evidence, voice break, ambiguous audience, fragile coupling.
NIT -- polish. Phrasing, micro-spacing, naming, redundancy.

Format per finding: <LOC>: [SEVERITY] <one-line problem>. <one-line fix>. <LOC> is file:line for code, <section> or <page> for prose/design.

Domain checklists

Software (code diff / PR)

Null & undefined handling, error paths, retry/backoff semantics.
Security boundaries: input validation, authz, secret leakage, path traversal.
Test coverage: happy path + at least one failure case per public surface.
Concurrency: race conditions, idempotency, ordering assumptions.
Public API: backward compatibility, types, naming.

Book chapter

Continuity with prior chapters (character state, world facts, timeline).
Voice / POV consistency.
Pacing: scene-vs-summary ratio, dwell on stakes.
Character beats: motivation legible, agency visible.
Stakes: what is at risk on this page, why now.

Campaign brief

Audience: named, specific, has a current alternative.
Message-to-channel fit: format matches where the audience already is.
CTA: single, frictionless, measurable.
KPI coverage: leading + lagging indicator named.
Kill criteria: the condition under which you stop spending.

Landing page (copy + layout)

Promise -> proof -> CTA alignment in the first viewport.
Mobile-readiness: tap targets >= 44px, no horizontal scroll, hero readable at 375px.
Accessibility: WCAG AA contrast 4.5:1 body / 3:1 large text; alt text on meaningful images; keyboard reachable CTA.
Conversion-path friction: number of decisions before primary CTA.

Design artifact (tokens / mockup)

Token consistency: every color/space/radius/shadow resolves to a defined token.
Contrast: WCAG AA on every text-on-surface pair.
Type scale: modular ratio respected; no orphan sizes.
Spacing rhythm: 4/8 baseline (or declared grid) respected.

Show full SKILL.md (201 more words)Show less

Output rules

Lead with BLOCK findings, then FLAG, then NIT.
No praise for meeting baseline expectations.
Max 10 findings unless the caller asks for exhaustive.
If nothing found: Clean. Reviewed <N> <units> across BLOCK/FLAG/NIT gates. No findings.

Artifact-write contract (MANDATORY)

Every review MUST write a REVIEW.md to a predictable path so the artifact is durable and resumable:

Software review of a planned unit of work: .planning/<milestone>/<phase-dir>/REVIEW.md
Software review without a planning context (ad-hoc PR): REVIEW.md at the repo root, or <branch>-REVIEW.md if reviewing a named branch.
Standalone artifact (chapter, brief, page, design file): write <artifact-basename>-REVIEW.md alongside the artifact. Example: chapter-7.md -> chapter-7-REVIEW.md.

REVIEW.md required sections

markdown

# Review: <artifact name>

Reviewed: <ISO-8601 timestamp>
Reviewer: ijfw-review
Domain: <software | book | campaign | landing | design>

## Summary
<2-4 sentences. Headline verdict + the single most important thing to fix.>

## BLOCK findings (must-fix)
- <LOC>: <one-line problem>. <one-line fix>.

## FLAG findings (should-discuss)
- <LOC>: <one-line problem>. <one-line fix>.

## NIT findings (polish)
- <LOC>: <one-line problem>. <one-line fix>.

If a section has no findings, keep the header and write (none) underneath -- absence is a signal, not a typo.

Second opinion

For high-stakes artifacts the caller can request a multi-lens audit via /cross-audit -- this fans the same artifact across Trident (codex / gemini / claude) and converges on a consensus verdict. Use it when stakes warrant a second pair of eyes.

Output contract

Emit a gate-result block as the LAST content of your output. Nothing after it. Use gate="swarm-review". Statuses: PASS | CONDITIONAL | WARN | FLAG | FAIL.

affected_artifacts MUST include the absolute path to the REVIEW.md that was written.

Format:

gate-result

{
  "schema_version": "1.0",
  "gate": "swarm-review",
  "status": "<STATUS>",
  "project_type": "<from project-type-detector>",
  "lenses": [],
  "affected_artifacts": ["<absolute path to REVIEW.md>"],
  "accounting": {"duration_ms": 0, "lenses_invoked": 0, "cost_usd": null},
  "remediation": [],
  "receipts_ref": null,
  "supersedes": null,
  "gate_id": "<gate-with-colons-replaced-by-dashes>-<ts>-<rand4>",
  "emitted_at": "<ISO-8601>"
}

Files

Just SKILL.md in claude/skills/ijfw-review of FerroxLabs/ijfw.

Open the folder on GitHubat commit eda62f3

Compare with similar skills

Ijfw Review 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.

Ijfw Review compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ijfw Review this skillFerroxLabs/ijfw	212	—	~1.2k	Automated safety check: Pass	MIT	6 days ago
Viral Product Evaluatorluongnv89/skills	131	—	~2.8k	Automated safety check: Pass	MIT	yesterday
React Code Reviewgiuseppe-trisciuoglio/developer-kit	357	—	~2.6k	Automated safety check: Notes	MIT	1 mo ago
Copy Project LifeVKirill/claude-lane-stack	122	—	~534	Automated safety check: Pass	MIT	2 days ago
Composer UIdxos/dxos	526	—	~9.3k	Automated safety check: Pass	Custom licence	yesterday
Frontend Design Deslopsamber/cc-skills	227	—	~4.9k	Automated safety check: Pass	MIT	9 days ago

Similar skills

Viral Product Evaluator
luongnv89/skills
Review a product codebase and landing page against 32 viral principles and produce a Virality Score plus ranked fixes.
131 GitHub stars~2.8k tokensUpdated yesterday
Frontend & DesignAuto-check passed
React Code Review
giuseppe-trisciuoglio/developer-kit
Provides comprehensive code review capability for React applications, validates component architecture, hooks usage, React 19 patterns, state management, performance optimization, accessibility…
357 GitHub stars~2.6k tokensUpdated 1 mo ago
Frontend & DesignAuto-check: notes
Copy Project Life
VKirill/claude-lane-stack
Карта файлов копирайта в .agents/copy/: шаблоны, статусы, цепочка audience→headlines→ux.
122 GitHub stars~534 tokensUpdated 2 days ago
Frontend & DesignAuto-check passed
Composer UI
dxos/dxos
A skill your agent uses when building or styling plugin UI with Composer's design system — the @dxos/react-ui packages.
526 GitHub stars~9.3k tokensUpdated yesterday
Frontend & DesignAuto-check passed
Frontend Design Deslop
samber/cc-skills
Designs distinctive, non-generic UI — typography, OKLCH color, design tokens (DESIGN.md), layout, components, motion, dark mode, accessibility — for landing pages, SaaS apps, dashboards, ecommerce…
227 GitHub stars~4.9k tokensUpdated 9 days ago
Frontend & DesignAuto-check passed
Enforce Design CI
hashgraph-online/awesome-codex-plugins
A skill your agent uses when a repository needs deterministic pull-request checks for new accessibility, design-token, component-structure, responsive, and UI-state regressions with file-level…
1.3k GitHub stars~541 tokensUpdated yesterday
Frontend & DesignAuto-check passed

Questions about Ijfw Review

What does Ijfw Review do?

A skill your agent uses when the user asks for a review of any artifact -- code diff, PR, book chapter, campaign brief, landing-page copy, or design tokens. Ijfw Review is an agent skill from FerroxLabs/ijfw. Use when the user asks for a review of any artifact -- code diff, PR, book chapter, campaign brief, landing-page copy, or design tokens.

When should I use Ijfw Review?

Ijfw Review fits situations like: the user asks for a review of any artifact -- code diff; landing-page copy.

How do I install Ijfw Review in Claude Code?

Run `npx skills add FerroxLabs/ijfw --skill ijfw-review -a claude-code`. Or copy the skill folder (claude/skills/ijfw-review in FerroxLabs/ijfw) into .claude/skills/ijfw-review in your project. Claude Code loads it when a task matches its description.

How do I install Ijfw Review in Codex?

Run `npx skills add FerroxLabs/ijfw --skill ijfw-review -a codex`. Or copy the skill folder (claude/skills/ijfw-review in FerroxLabs/ijfw) into .agents/skills/ijfw-review in your project. Codex loads it when a task matches its description.

Can I use Ijfw Review 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-review -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-review, .gemini/skills/ijfw-review, .github/skills/ijfw-review and .opencode/skills/ijfw-review in your project.

What does Ijfw Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Ijfw Review is instructions for the agent only.

Does Ijfw Review 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 Review 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 Review use?

Ijfw Review 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 Review use?

About 1.2k tokens (SKILL.md is roughly 5k 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 Review?

Skills that share tags, products or a category with Ijfw Review: Viral Product Evaluator (luongnv89/skills, 131 stars), React Code Review (giuseppe-trisciuoglio/developer-kit, 357 stars), Copy Project Life (VKirill/claude-lane-stack, 122 stars) and Composer UI (dxos/dxos, 526 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ijfw Review?

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.

Install Ijfw Review

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Severity vocabulary (all domains)

Domain checklists

Software (code diff / PR)

Book chapter

Campaign brief

Landing page (copy + layout)

Design artifact (tokens / mockup)

Output rules

Artifact-write contract (MANDATORY)

REVIEW.md required sections

Second opinion

Output contract

Files

Compare with similar skills

Similar skills

More from FerroxLabs/ijfw

Related

Questions about Ijfw Review