agentleFS
hmj1026hmj1026/dhpk/skills/project-audit/SKILL.md

project-audit

Skill2 starsChanged 6 days agoMITView on GitHub

Project health audit with deterministic scoring. Use when: evaluating project quality, onboarding to new codebase, periodic health checks. Not for: runtime performance analysis, security-specific audits (use change-verdict --mode security). Output: 5-dimension score + actionable findings.

15 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run node "$SKILL_DIR/scripts/audit.js" --json to collect deterministic scores

    line 25
  2. Distinctive:

    Add qualitative interpretation beyond the scores (e.g., "test ratio is good but concentrated in unit tests")

    line 30
  3. Distinctive:

    If the script fails, report the error and suggest running manually:

    line 61

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Project Audit

$SKILL_DIR denotes the physical directory containing the selected SKILL.md; it is path notation, not an ambient environment variable or repository-root lookup. Resolve it before running the audit from an arbitrary consumer cwd.

When NOT to Use

  • Security-specific review (use change-verdict --mode security)
  • Runtime performance profiling
  • Mid-development review (use change-verdict --mode code)

Procedure

  1. Run node "$SKILL_DIR/scripts/audit.js" --json to collect deterministic scores
  2. Parse the JSON output — overall_score, status, dimensions, checks, findings, next_actions
  3. If status = Blocked (P0 findings) — highlight critical gaps, suggest immediate fixes
  4. If status = Needs Work (P1 findings) — format improvement roadmap by dimension
  5. If status = Healthy — summarize strengths, note any P2 improvements
  6. Add qualitative interpretation beyond the scores (e.g., "test ratio is good but concentrated in unit tests")

Script Integration

The audit script runs 12 deterministic checks across 5 dimensions:

DimensionChecksWhat It Measures
oss2LICENSE, README quality
robustness3CI config, lint/typecheck, test ratio
scope2Declared features vs implementation, AC completion
runnability3Package manifest, scripts, env/Docker setup
stability2Lock file + audit, type configuration

Scoring Model

  • Each check: 1 (pass) / 0.5 (partial) / 0 (fail) / N/A (skipped)
  • Dimension score: applicable_sum / applicable_count * 100
  • Overall score: average of dimension scores
  • Confidence: applicable_checks / total_checks per dimension

Status Determination

StatusConditionExit Code
BlockedAny P0 finding2
Needs WorkNo P0, has P11
HealthyNo P0/P10

Script Failure Fallback

If the script fails, report the error and suggest running manually:

node "$SKILL_DIR/scripts/audit.js" --json

Output

## Project Audit Report

| Field | Value |
|-------|-------|
| Repo | [name] |
| Score | **[N]/100** |
| Status | [icon] [status] |

### Dimensions
[table of dimension scores]

### Checks
[list of check results with suggestions]

### Next Actions
[prioritized action items]

## Gate: ✅/⛔

References

  • references/check-catalog.md — Check definitions, scoring criteria, ecosystem detection (read when investigating a specific check result)
  • references/output-template.md — Report format examples and JSON schema (read when customizing output)

Verification

  • Script ran successfully
  • All 12 checks executed (or marked N/A with reason)
  • Qualitative interpretation added beyond raw scores
  • Next actions are actionable (include commands where applicable)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.