Agent skill

ForgeDock PR Review Adapter

by RapierCraftStudios in RapierCraftStudios/ForgeDock

Adapts a shared pull request review flow to the ForgeDock repository, with its own change categories, shell and installer checks, and optional sub-agent fan-out.

AGPL-3.0Auto-check passedDevelopment

Install ForgeDock PR Review Adapter

skills CLI
$ npx skills add RapierCraftStudios/ForgeDock --skill review-pr -a claude-code

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

GitHub CLI
$ gh skill install RapierCraftStudios/ForgeDock review-pr --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/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-pr .claude/skills/review-pr && 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/

Facts

Skill name
review-pr
GitHub stars
117
Token cost
~620 tokens
SKILL.md length
263 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Adapts a shared pull request review flow to the ForgeDock repository, with its own change categories, shell and installer checks, and optional sub-agent fan-out.

  • Reviewing a pull request in the forgedock repository
  • SKILL.md covers Forge Repo Review Override, Forge Review Categories, Forge Review Checks and Review Fan-Out, plus 1 more section
  • Calls bash
  • Checking installer and shell script changes in a Forge pull request

What it does

This is a repo-specific adapter for reviewing pull requests in the forgedock repository from Codex. It keeps the shared lifecycle in commands/review-pr.md for review phases, GitHub outputs and merge behavior, but drops assumptions about service paths such as services/api or web and keeps Forge pull requests out of the staging review route. Changed files are sorted into five groups: router and state-machine commands, nested pipeline modules, the runtime and installer layer, verification scripts, and docs with the changelog.

The Forge-specific checks are a bash -n syntax pass on changed shell scripts, a scan for stale references to old .claude paths or deleted docs, a mapping check that touched skill references still match installed forge skills, an installer check that install-codex.sh still generates namespaced skills without overwriting unrelated global ones, and changelog coverage for workflow changes. Sub-agents are used only when the diff justifies them. Output stays evidence-based, with structured findings, a GitHub comment summary and issues for real findings.

When your agent uses it

  • Reviewing a pull request in the forgedock repository
  • Checking installer and shell script changes in a Forge pull request
  • Verifying that changelog and docs match workflow changes in a Forge pull request

Example prompts

  • “Review the open forgedock pull request that changes install-codex.sh.”
  • “Run a Forge-aware review of this PR and summarize the findings in a GitHub comment.”
  • “Check whether this Forge PR left any stale .claude/commands references behind.”

Requirements

  • A checkout of the forgedock repository

What it can do on your machine

Read from SKILL.md and the folder at commit d89c6f2. 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

    Shell commands in SKILL.md call:

    • bash

    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

ForgeDock PR Review Adapter loads about 620 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 263 words of instructions outside code blocks.

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

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 RapierCraftStudios/ForgeDock at commit d89c6f2, republished under its AGPL-3.0 licence (© RapierCraftStudios). 263 words, ~620 tokens.

Download SKILL.mdSave it as .claude/skills/review-pr/SKILL.md (or your agent's skills folder).
name
review-pr
description
Review Forge pull requests from Codex with Forge-aware heuristics and the shared Forge verdict/merge model.

Forge Repo Adapter: review-pr

Use commands/review-pr.md as the lifecycle source for review phases, GitHub outputs, and merge semantics, but override the project-specific repo assumptions when the PR belongs to RapierCraftStudios/forgedock.

Forge Repo Review Override

For Forge repo PRs:

  • Do not require project-specific service paths like services/api, services/worker, or web/.
  • Do not depend on commands/review-pr-agents.md as an authoritative domain catalog; it remains reference-only for the shared command system.
  • Do not route Forge PRs into review-pr-staging solely because the base/head pair matches staging patterns. Continue in a Forge-aware full review flow in this adapter.

Forge Review Categories

Replace the shared command’s service/domain classification with these categories:

  • Router / state machine: commands/work-on.md, commands/orchestrate.md, commands/milestone.md, commands/review-pr.md
  • Nested pipeline modules: commands/work-on/**
  • Runtime / installer layer: install.sh, install-codex.sh, AGENTS.md, CLAUDE.md, docs/CODEX.md
  • Verification scripts: scripts/**
  • Docs / changelog alignment: docs/**, CHANGELOG.md

Forge Review Checks

Run the shared review lifecycle, but use Forge-relevant checks:

  • bash -n on changed shell scripts
  • stale reference scan for outdated .claude/commands, .claude/worktrees, deleted docs, or wrong repo-local paths
  • nested skill mapping sanity: Skill("work-on:...") / Skill("review-pr...") references touched by the PR still correspond to installed forge-* skills or repo-local adapters
  • installer sanity: if install-codex.sh changed, verify it still generates namespaced skills and does not overwrite unrelated global skills
  • changelog coverage for meaningful workflow behavior changes

Review Fan-Out

Use Codex sub-agents only when the diff justifies it. Good fan-out slices for Forge PRs are:

  • workflow/state-machine reviewer
  • GitHub/CLI integration reviewer
  • runtime/installer reviewer
  • docs/changelog reviewer

Output Contract

Keep the shared review-pr output behavior:

  • evidence-based findings only
  • structured findings when reporting issues
  • GitHub comment summary
  • issue creation for real findings
  • merge/approve behavior compatible with work-on/review

© RapierCraftStudios, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/review-pr of RapierCraftStudios/ForgeDock.

Open the folder on GitHubat commit d89c6f2

Compare with similar skills

ForgeDock PR Review Adapter 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.

ForgeDock PR Review Adapter compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
ForgeDock PR Review Adapter this skillRapierCraftStudios/ForgeDock117—~620Automated safety check: PassAGPL-3.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
GitHub Review Iterationprisma/orm48k—~2.2kAutomated safety check: PassApache-2.0
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Fastlane Pull Request Reviewfastlane/fastlane42k—~550Automated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed
  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Reviews a fastlane pull request against its linked issue and the project guides, separating blocking from non-blocking findings and handling vulnerabilities privately.

    42k GitHub stars~550 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Pull Request Babysitter

    thedotmack/claude-mem

    Keeps watching a pull request, fixing real review and CI problems and resolving stale threads, until it is clean and ready to merge.

    99k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from RapierCraftStudios/ForgeDock

  • Quality Gate

    RapierCraftStudios/ForgeDock

    Run a Forge-aware pre-commit quality gate from Codex. An agent skill from RapierCraftStudios/ForgeDock.

    117 GitHub stars~406 tokensUpdated today
    Auto-check passed
  • Work On

    RapierCraftStudios/ForgeDock

    Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.

    117 GitHub stars~750 tokensUpdated today
    Auto-check passed
  • Forge Issue Investigator

    RapierCraftStudios/ForgeDock

    Repo adapter that runs the investigation step of the ForgeDock work-on pipeline on a GitHub issue and posts a FORGE:INVESTIGATOR report comment.

    117 GitHub stars~457 tokensUpdated today
    Auto-check passed
  • Work On Review

    RapierCraftStudios/ForgeDock

    Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter.

    117 GitHub stars~436 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about ForgeDock PR Review Adapter

What does ForgeDock PR Review Adapter do?

Adapts a shared pull request review flow to the ForgeDock repository, with its own change categories, shell and installer checks, and optional sub-agent fan-out. This is a repo-specific adapter for reviewing pull requests in the forgedock repository from Codex.md for review phases, GitHub outputs and merge behavior, but drops assumptions about service paths such as services/api or web and keeps Forge pull requests out of the staging review route.

When should I use ForgeDock PR Review Adapter?

ForgeDock PR Review Adapter fits situations like: reviewing a pull request in the forgedock repository; checking installer and shell script changes in a Forge pull request; verifying that changelog and docs match workflow changes in a Forge pull request.

How do I install ForgeDock PR Review Adapter in Claude Code?

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

How do I install ForgeDock PR Review Adapter in Codex?

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

Can I use ForgeDock PR Review Adapter 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 RapierCraftStudios/ForgeDock --skill review-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-pr, .gemini/skills/review-pr, .github/skills/review-pr and .opencode/skills/review-pr in your project.

What does ForgeDock PR Review Adapter need to run?

Going by SKILL.md and its folder, ForgeDock PR Review Adapter needs the command-line tools its instructions call (bash). Our summary lists: A checkout of the forgedock repository.

Does ForgeDock PR Review Adapter 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 ForgeDock PR Review Adapter 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 ForgeDock PR Review Adapter use?

ForgeDock PR Review Adapter is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does ForgeDock PR Review Adapter use?

About 620 tokens (SKILL.md is roughly 2.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 ForgeDock PR Review Adapter?

Skills that share tags, products or a category with ForgeDock PR Review Adapter: PR Babysitter (openinterpreter/openinterpreter, 69k stars), GitHub Review Iteration (prisma/orm, 48k stars), PR Review State Fetch (prisma/orm, 48k stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains ForgeDock PR Review Adapter?

RapierCraftStudios (a GitHub organization) maintains it in RapierCraftStudios/ForgeDock, which has 117 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.

Source: RapierCraftStudios/ForgeDock on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.