Skip to content

jezweb/claude-skills / plugins/dev-tools/skills/project-health

project-health

Verified

All-in-one project configuration and health management. Sets up new projects (settings.local.json, CLAUDE.md, .gitignore), audits existing projects (permissions, context quality, MCP coverage, leaked secrets, stale docs), tidies accumulated cruft, captures session learnings, and adds permission presets. Uses sub-agents for heavy analysis to keep main context clean. Trigger with 'project health', 'check project', 'setup project', 'kickoff', 'bootstrap', 'tidy permissions', 'clean settings', 'capture learnings', 'audit context', 'add python permissions', or 'init project'.

FileKindSize
SKILL.mdskill md11.7 KB
references/commit-hook.mdmarkdown1.6 KB
references/permission-presets.mdmarkdown24.1 KB
references/project-types.mdmarkdown5.2 KB
references/quality-criteria.mdmarkdown2.8 KB
references/templates.mdmarkdown6.7 KB

references/commit-hook.md

View on GitHub
# Recommended Hook: Context Capture on Commit

Automatically remind Claude to capture learnings after every git commit. This pairs with Mode 1 (Session Capture) — the hook triggers the prompt, the skill handles the capture.

## Setup

Create this file at `~/.claude/hookify.context-capture-reminder.local.md` for global coverage, or `project/.claude/hookify.context-capture-reminder.local.md` for a single project:

```markdown
---
name: context-capture-reminder
enabled: true
event: bash
pattern: git\s+commit
action: warn
---

Context check: Were any patterns, gotchas, or commands discovered during this work that should be captured to CLAUDE.md or .claude/rules/? If yes, update them now before moving on. If nothing new was learned, carry on.
```

## How It Works

1. You finish work and commit
2. The hook fires after the `git commit` Bash call
3. Claude pauses to consider whether anything learned during this work should be persisted
4. If yes, Claude updates CLAUDE.md or creates/updates a `.claude/rules/` file
5. If nothing new, Claude continues

## Why Commit Time?

- Context is fresh — you just finished the work
- You're creating a permanent record anyway
- Natural checkpoint before moving to the next task
- Pairs with `git log` for tracing when a pattern was discovered

## Requires

This hook uses the [hookify](https://github.com/jezweb/claude-skills) plugin for Claude Code. If you don't have hookify, you can add the same reminder as a line in your CLAUDE.md:

```markdown
## Workflow
- Before committing: check if any discoveries should be captured to CLAUDE.md or .claude/rules/
```
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall