project-maturation

Audits codebases across eight quality dimensions and generates phased improvement plans.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill project-maturation-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-maturation
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/project-maturation
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill project-maturation-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects often accumulate technical debt across tests, CI, security, and documentation without a clear picture of where they stand or what to fix first. This Skill provides a structured audit that scores codebase maturity and produces a prioritized, phase-by-phase remediation plan. ## Core Features & Use Cases - Stack Detection: Identifies the language, build tool, and CI system from project files like go.mod, package.json, pyproject.toml, and GitHub Actions workflows. - Maturity Scoring: Scores eight dimensions (tests, CI/CD, types/linting, error handling, docs, security, architecture, observability) on a 0-3 scale and presents a maturity matrix. - Phased Remediation Plan: Generates prioritized phases ordered by impact, with security and tests first, executed one phase at a time with CI verification between phases. - Use Case: Before a first public release of a Python project, run the audit to discover missing dependency scanning and thin test coverage, then follow the generated plan to reach release-ready maturity. ## Quick Start Audit this repository for maturity across tests, CI, security, and documentation, then generate a prioritized improvement plan.

Frequently Asked Questions about project-maturation

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

FAQPage Schema
How do I audit a codebase for quality and technical debt?

Run a structured maturity audit that detects your stack, then scores tests, CI/CD, linting, error handling, docs, security, architecture, and observability on a 0-3 scale. The result is a maturity matrix with a prioritized remediation plan ordered by impact.

What should I fix first when hardening a project before release?

Prioritize by impact: security gaps first, then tests as a safety net, then CI/CD automation, followed by linting, error handling, architecture, docs, and observability. Each phase should pass CI before starting the next.

Does the maturity audit work for Go, Python, and Node.js projects?

Yes, the audit detects the stack from manifest files like go.mod, pyproject.toml, package.json, Cargo.toml, and pom.xml, then adapts its checks to stack-appropriate tools such as pytest, golangci-lint, eslint, or shellcheck.

How is project maturity scored in a codebase audit?

Each dimension is scored 0-3: 0 means absent, 1 means basic or inconsistent, 2 means solid coverage of happy paths, and 3 means comprehensive and automated. Scores are summed into an overall maturity percentage.

When should I not mix security fixes with test improvements?

Never mix them in the same phase. The audit enforces one phase at a time with atomic PRs of roughly 300 lines, so each change set stays reviewable and CI verifies no regressions before the next phase begins.