codebase-check

Orchestrates read-only codebase audits followed by user-approved fixes and verification.

2|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/ShineBreaker/Guix-configs --skill codebase-check-shinebreaker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-check
Source: https://github.com/ShineBreaker/Guix-configs/tree/main/dotfiles/mutable/agents/skills/.config/agents/skills/codebase-check
Command: npx skills add https://github.com/ShineBreaker/Guix-configs --skill codebase-check-shinebreaker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large codebases accumulate dead code, dependency drift, missing regression tests, and stale architecture rules. This Skill provides a structured, gated workflow that audits a repository read-only, lets the user pick which findings to fix, then executes and verifies each fix one at a time. ## Core Features & Use Cases - Read-only audit phase: Runs architecture analysis via peer skills, produces an HTML report in the system temp directory, and never writes to the repository before user approval. - User selection gate: Merges audit findings with hygiene checks (regression test gaps, stale rules files, scope creep, cross-artifact inconsistency) into one candidate list; only explicitly selected items are executed. - Gated execution and verification: Applies TDD for behavior changes, keeps refactorings green, runs code review before each conventional commit, and confirms a five-state release check when deliverables are touched. - Use Case: Ask for a codebase tidy-up before a release: the Skill audits dependencies and dead code, you pick three candidates, and it fixes each with tests, commits, and a final aggregate verification. ## Quick Start Explicitly invoke the codebase-check skill by name and ask it to run a full codebase tidy-up audit on the current workspace.

Frequently Asked Questions about codebase-check

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

FAQPage Schema
How do I run a structured codebase cleanup audit?▼

Explicitly invoke the codebase-check skill by name in your workspace. It performs a read-only audit, presents a merged candidate list of findings, and only executes fixes on items you explicitly select, verifying each one before moving on.

What does the codebase audit check for?▼

The audit covers dependency drift, dead code, architecture friction points, missing regression tests for recent bug fixes, stale or missing module rules files, speculative configuration creep, and inconsistencies across docs, generated artifacts, and configs.

Does the audit modify my repository automatically?▼

No. Steps before user selection are strictly read-only, and the HTML report is written to the system temp directory, never the repo. Deletions and changes happen only after you explicitly approve each candidate.

When should I not use this cleanup workflow?▼

Skip it for a single known issue, which should just be fixed directly. The workflow is designed for multi-stage structured cleanups like dependency audits, dead code sweeps, and architecture reviews, not one-off bug fixes.

How are fixes verified before completion?▼

Each candidate must pass tests and the repository's aggregate check before the next begins. When changes touch release artifacts, a five-state check confirms local code, git commit, signed artifact, deployed files, and what users actually receive.