bubbles-repo-readiness

Audits repository onboarding docs and documented commands against real repo command surfaces.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-repo-readiness-pkirsanov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bubbles-repo-readiness
Source: https://github.com/pkirsanov/bubbles/tree/main/skills/bubbles-repo-readiness
Command: npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-repo-readiness-pkirsanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories often drift out of sync with their own documentation: onboarding guides reference dead files, README commands no longer match real build or test entrypoints, and agent-facing guidance becomes stale. This Skill verifies repo readiness with evidence-based checks instead of assumptions, while keeping hygiene findings separate from certification gates. ## Core Features & Use Cases - Onboarding Doc Drift Detection: Scans high-signal onboarding and architecture docs for broken local file references and missing entrypoint documentation. - Command Truth Verification: Compares documented build, test, lint, and run commands against the repo's real command registry and installed framework surfaces. - Advisory Gap Classification: Reports findings by severity and effort as advisory repo-readiness gaps, never as certification failures. - Use Case: Before onboarding AI agents to a new project, run this audit to confirm the README's setup commands actually work, the architecture docs link to real files, and minimal agent guidance exists. ## Quick Start Audit this repository for agent-readiness by checking onboarding docs for dead links and verifying documented commands against real repo entrypoints.

Frequently Asked Questions about bubbles-repo-readiness

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

FAQPage Schema
How do I check if my repo is ready for AI coding agents?▼

Run a repo-readiness audit that inspects onboarding and architecture docs, verifies documented commands against real repo entrypoints, and confirms minimal agent guidance exists. Findings are classified as advisory gaps with severity and effort estimates.

How to find broken links in repository documentation?▼

The audit scans high-signal onboarding and architecture docs for local file references and checks each one for dead links. Broken references are reported as repo-readiness findings, ordered by severity and remediation effort.

Does repo readiness checking affect certification status?▼

No. Repo-readiness findings are strictly advisory and are never treated as certification failures or promotion gates. The audit explicitly separates repo hygiene from certification state such as state.json certification fields.

Can I use this audit on any programming language or framework?▼

Yes. The checks are project-agnostic and portable by design. Language-specific or ecosystem-specific rules are never hardcoded as universal requirements; command truth is resolved from each repo's own command registry.

What are the limitations of a repo-readiness audit?▼

It does not evaluate spec or scope completion, build quality beyond what the repo already governs, or certification status. It also does not require AGENTS.md as a universal index and skips product-direction checks for infrastructure repos.