repo-b-preflight-doc-sync

Automate PR preflight governance and documentation lockstep for Git repositories.

2|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/grtninja/skill-arbiter --skill repo-b-preflight-doc-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-b-preflight-doc-sync
Source: https://github.com/grtninja/skill-arbiter/tree/main/skill-candidates/repo-b-preflight-doc-sync
Command: npx skills add https://github.com/grtninja/skill-arbiter --skill repo-b-preflight-doc-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enforce PR readiness governance and documentation lockstep. Use before PRs to run required validation profiles and keep README.md, docs/PROJECT_SCOPE.md, and docs/SCOPE_TRACKER.md synchronized with shipped behavior.

Core Features & Use Cases

  • PR readiness governance and gating before PR submission
  • Documentation lockstep to keep README.md, docs/PROJECT_SCOPE.md, and docs/SCOPE_TRACKER.md in sync
  • Evidence capture with explicit repro notes for preflight runs
  • Loopback routing to re-run updated checks when issues are unresolved

Quick Start

Run the preflight and docs-lockstep workflow before submitting PRs to validate required gates and synchronize documentation.

Frequently Asked Questions about repo-b-preflight-doc-sync

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

FAQPage Schema
How do I enforce documentation lockstep before submitting a pull request?

Documentation lockstep is enforced by validating that README.md, docs/PROJECT_SCOPE.md, and docs/SCOPE_TRACKER.md remain synchronized with shipped behavior during PR preflight governance checks.

What is PR preflight governance for Git repositories?

PR preflight governance is the process of running required validation profiles and gating rules on targeted changes to ensure documentation alignment and readiness before a pull request is submitted.

How do I keep README and project scope docs synchronized with code changes?

You can keep documentation synchronized by running an automated preflight workflow that validates README.md, docs/PROJECT_SCOPE.md, and docs/SCOPE_TRACKER.md against the actual changes shipped in your repository.

Can I run preflight validation profiles without additional dependencies?

Yes, the preflight validation operates with no external dependencies, running required governance gates and documentation alignment checks directly within your version-control workflow.

What happens when a preflight check fails during PR readiness validation?

When a preflight check fails, loopback routing triggers to re-run updated checks, allowing you to capture explicit repro notes and resolve issues before final PR submission.

Do I need frontmatter metadata in SKILL.md for preflight gating?

Yes, the preflight governance requires frontmatter metadata in SKILL.md, specifically enforcing the name and description fields, while supporting optional components like scripts, references, and assets.