fabrik-review

Reviews implementation PRs, fixes issues, and prepares branches for human merge.

22|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/handarbeit/fabrik --skill fabrik-review-handarbeit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabrik-review
Source: https://github.com/handarbeit/fabrik/tree/main/plugin/fabrik-workflows/skills/fabrik-review
Command: npx skills add https://github.com/handarbeit/fabrik --skill fabrik-review-handarbeit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automates the code review stage of a GitHub-driven SDLC pipeline, ensuring pull requests are rebased, tested, and cleaned up before a human reviewer spends time on them. ## Core Features & Use Cases - Automated PR Review and Fixing: Reads the diff against the resolved base branch, checks correctness, testing, security, and code quality, then commits a fix for each issue found. - Rebase and Conflict Management: Rebases onto the correct base branch only when behind, resolves merge conflicts conservatively, and pushes with force-with-lease safety. - External Feedback Handling: Processes review bot and human PR comments, applies a strict exposure-assessment bar for security-relevant findings, and can spawn blocking child issues via engine markers. - Use Case: An issue's implementation stage finishes and opens a draft PR; this skill reviews the diff, fixes a swallowed error path, verifies the test suite passes with a timeout, and signals stage completion so the engine marks the PR ready for human review. ## Quick Start Act as the Fabrik Review stage agent for the current issue worktree: read the .fabrik-context files, rebase if behind, review and fix the diff, then emit FABRIK_STAGE_COMPLETE when the PR is ready.

Frequently Asked Questions about fabrik-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review in a GitHub-based CI pipeline?

Use a review stage agent that reads the PR diff against the base branch, checks correctness, testing, security, and conventions, then commits a fix per issue. This skill performs that loop and signals completion to the Fabrik engine when the PR is ready.

How should an automated reviewer handle merge conflicts during rebase?

Rebase only when the branch is behind, resolve conflicts conservatively by never dropping base-branch code, and run the build after each resolution. Push with force-with-lease and never use git reset --hard to match the remote.

Can the review agent respond to bot review comments like Copilot or Gemini?

Yes, it checks PR comments before its own review and addresses valid feedback. Security-relevant findings require an explicit exposure assessment covering reachability, trigger conditions, and existing mitigations before dismissal.

What happens if the review finds an issue it cannot fix?

The agent does not emit the completion marker and instead describes the blocker clearly. It can also spawn a blocking child issue via FABRIK_SPAWN_CHILD markers, which the engine links as a blocked_by dependency.

Why must tests always run with a timeout in automated stages?

A single hanging test blocks the headless stage indefinitely since no interactive session exists to intervene. The skill mandates framework-level timeouts like go test -timeout or pytest --timeout for every suite run.