fabrik-validate

Validates pull requests against issue requirements before merge in the Fabrik pipeline.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull requests in an automated SDLC pipeline can reach merge review without anyone confirming the implementation actually matches the original issue spec, that tests still pass after rebasing, or that no regressions were introduced. This Skill acts as the final quality gate in the Fabrik pipeline, verifying requirements, tests, and branch state before a human merges. ## Core Features & Use Cases - Requirements Verification: Reads the original issue spec from .fabrik-context/ files and checks each requirement against the implementation, producing a pass/fail checklist. - Safe Rebase and Conflict Handling: Resolves the PR's base branch dynamically, skips unnecessary rebases, resolves merge conflicts conservatively, and never discards base-branch code. - Test and Regression Validation: Runs the full test suite with mandatory timeouts, race detection, build, and vet checks, then reports results in a structured validation report. - Merge-Queue and CI Freshness Gates: Checks merge-queue membership and required-check freshness via GraphQL before rebasing to avoid ejecting queued PRs or livelocking CI. - Use Case: An issue's implementation passed code review, but the base branch moved twice since. The Validate agent rebases safely, reruns tests, verifies every requirement from the issue body, and emits the completion marker only when the PR is genuinely ready to merge. ## Quick Start Act as the Fabrik Validate stage agent and verify that the current pull request meets all requirements in the issue spec, passes the full test suite, and is ready to merge.

Frequently Asked Questions about fabrik-validate

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

FAQPage Schema
How do I validate a pull request against issue requirements before merging?

Read the original issue spec from .fabrik-context/issue.md, then verify each requirement against the implementation with a pass/fail checklist. Run the full test suite with a timeout, check for regressions, and confirm the branch is rebased and pushed before declaring the PR ready to merge.

How do I safely rebase a PR branch onto a moving base branch?

First resolve the base branch with gh pr view, then check if the branch is actually behind using git rev-list --count before rebasing. After a clean rebase, push with git push --force-with-lease and never use git reset --hard to match the remote, since that discards the rebase.

Why should I skip rebasing when a PR is in a merge queue?

Rebasing a queued PR ejects it from the merge queue and burns an enqueue cycle that nothing downstream can undo. Query isInMergeQueue via GraphQL before rebasing, and treat any unreadable result as queued to fail toward safety.

Can I run a dev server in the background during automated validation?

No, backgrounded processes survive the stage and become orphaned processes holding ports. Prefer one-shot build commands, bracket live servers with trap-based teardown in a single command, or bound them with a timeout so they self-terminate.

What happens if validation finds the PR depends on other unfinished work?

Declare a blocking dependency using the FABRIK_SPAWN_CHILD_BEGIN/END markers instead of running gh issue create directly. The engine creates the child issue, adds it to the board, and links it as a blocked_by dependency, and you must not emit the completion marker in the same response.