How do I install the Repo B Preflight Doc Sync skill?

Run npx skillmds@latest add tomevault-io/repo-b-preflight-doc-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Repo B Preflight Doc Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Repo B Preflight Doc Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Repo B Preflight Doc Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo B Preflight Doc Sync?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo B Preflight Doc Sync by tomevault-io

Name: Repo B Preflight Doc Sync
Author: tomevault-io

Repo B Preflight Doc Sync

Enforce <PRIVATE_REPO_B> preflight gates 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. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

REPO_B Shim Preflight and Doc Sync

Use this skill for PR-readiness and governance updates.

Workflow

Run required preflight commands for the change scope.
Capture command evidence and failures with explicit repro notes.
Keep docs in lockstep for behavior changes.
- include repo-local reconciliation docs when the repo is carrying major unreleased open diffs
- include startup/state-persistence docs when launch behavior changed
Add target-PC rerun steps when hardware-only checks cannot run locally.

Scope Boundary

Use this skill for release-readiness gate execution and docs synchronization before PRs.

Do not use this skill for:

Runtime agent bridge behavior debugging.
Hybrid Windows/WSL connectivity diagnosis.
Strict hardware probe root-cause workflows.

Required Preflight Profiles

pwsh -File tools/preflight.ps1
pwsh -File tools/preflight.ps1 -Fast
pwsh -File tools/preflight.ps1 -Node
pwsh -File tools/preflight.ps1 -Hardware -ForceReal -MemryxOnly -VerboseOutput

python tools/preflight.py

Documentation Lockstep

Review and update together when behavior changes:

README.md
docs/PROJECT_SCOPE.md
docs/SCOPE_TRACKER.md
repo-local reconciliation/startup notes when present

References

PR gate checklist: references/pr-gate-checklist.md

Loopback

If this lane is unresolved, blocked, or ambiguous:

Capture current evidence and failure context.
Route back through $skill-hub for chain recalculation.
Resume only after the updated chain returns a deterministic next step.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: repo-b-preflight-doc-syncdescription: Enforce <PRIVATE_REPO_B> preflight gates 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. Use when this capability is needed.---# REPO_B Shim Preflight and Doc SyncUse this skill for PR-readiness and governance updates.## Workflow1. Run required preflight commands for the change scope.2. Capture command evidence and failures with explicit repro notes.3. Keep docs in lockstep for behavior changes. - include repo-local reconciliation docs when the repo is carrying major unreleased open diffs - include startup/state-persistence docs when launch behavior changed4. Add target-PC rerun steps when hardware-only checks cannot run locally.## Scope BoundaryUse this skill for release-readiness gate execution and docs synchronization before PRs.Do not use this skill for:1. Runtime agent bridge behavior debugging.2. Hybrid Windows/WSL connectivity diagnosis.3. Strict hardware probe root-cause workflows.## Required Preflight Profiles```powershellpwsh -File tools/preflight.ps1pwsh -File tools/preflight.ps1 -Fastpwsh -File tools/preflight.ps1 -Nodepwsh -File tools/preflight.ps1 -Hardware -ForceReal -MemryxOnly -VerboseOutput``````bashpython tools/preflight.py```## Documentation LockstepReview and update together when behavior changes:- `README.md`- `docs/PROJECT_SCOPE.md`- `docs/SCOPE_TRACKER.md`- repo-local reconciliation/startup notes when present## References- PR gate checklist: `references/pr-gate-checklist.md`## LoopbackIf this lane is unresolved, blocked, or ambiguous:1. Capture current evidence and failure context.2. Route back through `$skill-hub` for chain recalculation.3. Resume only after the updated chain returns a deterministic next step.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/grtninja) — claim your Tome and manage your conversions.

Frequently asked questions