checkhealth

Inventory project files, stack, lifecycle signals, and risks for a health report.

Updated Aug 23, 2026

Search Tags:#dependency analysis #test coverage #risk assessment #repository health #project audit #build readiness #lifecycle stage

Ready to run

npx skills add https://github.com/bugabinga/pi-ext --skill checkhealth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checkhealth
Source: https://github.com/bugabinga/pi-ext/tree/main/skills/checkhealth
Command: npx skills add https://github.com/bugabinga/pi-ext --skill checkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you quickly understand what state a software project is really in, so you can plan next steps instead of guessing.

Core Features & Use Cases

Repo inventory and lifecycle mapping: Detects the project shape, stack, and whether it’s prototype, active development, maintenance, production, or abandoned.
Evidence-first status assessment: Separates observed facts from inferences by checking docs, tooling, and test/build signals.
Safety-focused health checks: Prefers static inspection and lightweight read-only commands, avoiding installs, migrations, servers, or destructive actions.
Blunt action planning: Produces risks/blockers and a concrete next 3–7 step roadmap.

Quick Start

Ask: run checkhealth on the current repository to produce a fact-first status report and recommended next actions.

Frequently Asked Questions about checkhealth

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

FAQPage Schema

How do I audit a repository to determine its lifecycle stage and build readiness?▼

Assess repository health by performing a fast, read-only inspection of the project's files, stack, and tooling signals. This inventory distinguishes observed facts from inferences to map the lifecycle stage, estimate done-versus-TODO tasks, and produce a concrete next-step roadmap.

What is the best way to inventory TODOs and assess project health without running destructive commands?▼

Inventory TODOs and assess project health using static inspection and lightweight read-only commands. This safety-focused method avoids executing installs, migrations, or servers, ensuring a fact-first status assessment that separates observed evidence from inferred risks.

Can I check dependency analysis and test coverage for a codebase without installing packages?▼

Yes, you can evaluate dependency analysis and test coverage without installing packages by preferring static inspection. The read-only assessment examines the repository's tooling health, configuration files, and project structure directly to determine build readiness.

Does a project audit work for identifying blockers and planning next actions in an unfamiliar codebase?▼

Yes, a project audit works for identifying blockers by inventorying files and lifecycle signals. It helps you quickly understand what state an unfamiliar software project is really in, producing a blunt action plan with a concrete 3 to 7 step roadmap.