Skip to content
Back to skills

Iterative Health Check

ASecurity

One-time audits don't track improvement:

  • 4 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 3, 2026
ai-agentsjavascriptjavasecuritydocumentation

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add fabioc-aloha/Alex_Skill_Mall --skill iterative-health-check --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Iterative Health Check?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Iterative Health Check
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fabioc-aloha-iterative-health-check/badge)](https://www.skillsdirectory.com/skills/fabioc-aloha-iterative-health-check)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: iterative-health-check
description: "One-time audits don't track improvement:"
lastReviewed: 2026-04-30
---

# Iterative Health-Check Loop

## The Problem

One-time audits don't track improvement:

- "We found 47 issues" — so what?
- No prioritization
- No follow-through
- Same issues reappear

## The Solution

Score → Fix Top Issues → Rescore loop.

```
┌──────────────────┐
│   Score          │ Assess current state quantitatively
└────────┬─────────┘
         ▼
┌──────────────────┐
│   Prioritize     │ Rank by ROI (impact / effort)
└────────┬─────────┘
         ▼
┌──────────────────┐
│   Fix Top N      │ Address highest-ROI issues
└────────┬─────────┘
         ▼
┌──────────────────┐
│   Rescore        │ Measure improvement
└────────┬─────────┘
         │
         └─────────► Repeat
```

## Scoring Framework

```javascript
const dimensions = {
  testCoverage: { weight: 0.25, score: 0 },
  docAccuracy: { weight: 0.20, score: 0 },
  securityGaps: { weight: 0.30, score: 0 },
  techDebt: { weight: 0.25, score: 0 }
};

function calculateHealth() {
  return Object.values(dimensions)
    .reduce((sum, d) => sum + d.weight * d.score, 0);
}

// Score each dimension 0-100
dimensions.testCoverage.score = 72;  // 72% coverage
dimensions.docAccuracy.score = 85;   // 85% of docs verified
dimensions.securityGaps.score = 60;  // 3 medium issues
dimensions.techDebt.score = 45;      // High debt

console.log(`Health: ${calculateHealth().toFixed(0)}%`); // 64%
```

## ROI Prioritization

```markdown
| Issue | Impact (1-5) | Effort (1-5) | ROI | Priority |
|-------|--------------|--------------|-----|----------|
| Fix auth bug | 5 | 2 | 2.5 | 1 |
| Add tests | 3 | 3 | 1.0 | 3 |
| Update deps | 4 | 2 | 2.0 | 2 |
| Refactor X | 2 | 4 | 0.5 | 4 |
```

ROI = Impact / Effort. Fix highest ROI first.

## Progress Tracking

```markdown
## Health Check History

| Date | Score | Top Fix | Impact |
|------|-------|---------|--------|
| 2026-04-01 | 45% | Security patch | +12% |
| 2026-04-15 | 57% | Test coverage | +8% |
| 2026-04-29 | 65% | Doc update | +5% |
```

## Verification

1. Score is reproducible (same method each time)
2. Fixes address highest-ROI issues
3. Rescore shows measurable improvement
4. Loop continues until target score reached

## When to Apply

- Codebase health monitoring
- Documentation audits
- Security reviews
- Any quality improvement initiative

## Tags

`quality` `audit` `metrics` `continuous-improvement`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…