quality-project-health

Analyze git history, test results, and task progress to score project health from 0-10.

7|Updated May 28, 2026
One-click install
npx skills add https://github.com/zcaceres/skills --skill quality-project-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-project-health
Source: https://github.com/zcaceres/skills/tree/main/skills/quality-project-health
Command: npx skills add https://github.com/zcaceres/skills --skill quality-project-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity of project status by providing an objective, evidence-based health rating from 0-10, helping developers and managers identify blockers and maintenance needs.

Core Features & Use Cases

  • Automated Health Audit: Inspects git state, validation commands, and project metadata to generate a comprehensive status report.
  • Work-Tracker Integration: Automatically pulls data from GitHub Project boards or local configuration files to assess task progress.
  • Use Case: Use this before a sprint review or when joining a new repository to quickly understand the project's stability, test coverage, and backlog health.

Quick Start

Invoke the quality-project-health skill to generate a status report and health rating for the current repository.

Frequently Asked Questions about quality-project-health

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

FAQPage Schema
How do I assess software project health and code quality?

Assess project health by analyzing git history, validation test results, and task board progress. This generates an evidence-based 0-10 quality score to help identify blockers and maintenance needs.

Can I use git history to generate a project quality score?

Yes, you can generate a project quality score by evaluating git state alongside validation commands and project metadata. This provides a quantitative 0-10 rating reflecting repository stability and backlog health.

Does project health auditing require access to task management metadata?

Yes, project health auditing requires read-only access to task management metadata, project configuration files, and git history to automatically pull data from GitHub Project boards or local files for evaluation.

What's the best way to audit project stability before a sprint review?

The best way to audit project stability before a sprint review is to run an automated health check that inspects git state, validation test results, and task board progress to generate a comprehensive status report.

When should I not rely on an automated project health rating?

You should not rely on an automated project health rating when lacking local development environments, git access, or project configuration files, as the evaluation requires this repository evidence to function.