verify-bootstrap

Analyze groundrules-bootstrapped project coherence and version signatures.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/lozit/groundrules --skill verify-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-bootstrap
Source: https://github.com/lozit/groundrules/tree/main/skills/verify-bootstrap
Command: npx skills add https://github.com/lozit/groundrules --skill verify-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

verify-bootstrap identifies coherence issues in a groundrules-bootstrapped project before a release or significant edits, ensuring consistency across version signatures, placeholder content, and file integrity.

Core Features & Use Cases

  • Consistency Checks: Verifies file versioning, identifies placeholder placeholders, ensures appropriate file structure, and checks Git initialization.
  • Coherence Assessment: Performs comprehensive checks for any signs of corruption or deviation from expected standards.
  • Fix Mode: Supports the --fix option for applying auto-corrections like version signature updates, without modifying the .groundrules.json state file.
  • Use Case: Before deploying a release candidate, run verify-bootstrap to confirm everything is in order for a smooth transition to production.

Quick Start

Use the verify-bootstrap skill to check the coherence of your groundrules-bootstrapped project: run /groundrules:verify-bootstrap

Frequently Asked Questions about verify-bootstrap

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

FAQPage Schema
How do I check the version consistency of a groundrules-bootstrapped project?

You can check version consistency by running the verify-bootstrap skill, which analyzes project bootstrapping details, file content, and structural coherence to identify any deviations from expected standards before a release.

What is the best way to verify file integrity and placeholder content in my project before deployment?

The best way to verify file integrity and identify placeholder content is to run a coherence assessment using verify-bootstrap, ensuring everything is in order for a smooth transition to production.

Can I automatically fix version signature issues during a project consistency check?

Yes, you can use the --fix option with verify-bootstrap to apply auto-corrections like version signature updates, without modifying the .groundrules.json state file.

Do I need a .groundrules.json file to run a project health and consistency check?

Yes, verify-bootstrap requires the .groundrules.json file and a bootstrapped project structure to perform comprehensive checks for corruption, file versioning, and Git initialization.

Why does my groundrules-bootstrapped project fail coherence checks before a release?

Coherence checks fail when verify-bootstrap detects issues like mismatched version signatures, leftover placeholder content, or structural deviations from expected bootstrapping standards.

When should I run a project consistency check on a bootstrapped repository?

You should run verify-bootstrap before a release or significant edits to confirm file versioning, structural coherence, and Git initialization are intact for a smooth production transition.