Menu
Auto-detect and run formatters, linters, type checkers, and tests for the current project. Use when validating a project, running all checks, checking code quality before committing, or verifying the build passes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Sync this Claude Code config against new release notes — find config features added since the pinned baseline that this config should adopt. Use when Claude Code has been updated, when the user asks what's new / what changed / whether to adopt new settings or hooks, after a version bump, or when checking config currency against the latest release. Reports adoptable settings/hooks/env-vars/permissions as a risk-tiered proposal, then bumps the baseline. Do NOT use for auditing existing config quality, debugging hooks, or organizing rules — that is `maintaining-claude-code`.
Monitor and watch GitHub Actions CI/CD pipeline runs in real time. Use when the user has pushed code and wants to watch the build, check CI status, see if tests passed, monitor a pipeline, or wait for a workflow run to complete. Also use after any `jj git push` or `git push` command. Reports pass/fail with failed job logs. Do NOT use for writing or editing CI workflow YAML files, optimizing CI config, or debugging CI configuration — only for monitoring active runs.
Reorganize and clean up messy commit history on a feature branch into logical, reviewable commits. Use when cleaning up commits, preparing a branch for review, separating formatting from logic changes, fixing broken intermediate states, or squashing WIP commits.
Audit and improve Claude Code hooks, rules, and settings.json. Use when adding/debugging a hook, organizing rules, auditing settings.json (permissions, env vars, stale flags), or deciding between hook vs skill vs rule vs CLAUDE.md. For SKILL.md authoring use the skill-creator plugin; for CLAUDE.md audits use the claude-md-improver plugin.
Execute a structured test plan and emit a concise results document (JSON + Markdown). Use when running test plans, executing QA workflows, verifying acceptance criteria systematically, or producing test results documentation.
Search past Claude Code sessions to recall prior solutions, commands, fixes, and decisions. Use when the user references earlier work ("how did I fix", "last time we", "pick up where we left off", "a few months ago", "what was that … I set up", "didn't I once").
| name | validating-project |
| description | Auto-detect and run formatters, linters, type checkers, and tests for the current project. Use when validating a project, running all checks, checking code quality before committing, or verifying the build passes. |
| context | fork |
| model | claude-haiku-4-5 |
Auto-detect project tooling and run validation steps in the correct order.
./CLAUDE.md for validation tools and project permissionsmake format && make lint && make typecheck && make test
Or make validate if available.
uv run ruff format .
uv run ruff check .
uv run ty check # or uv run mypy, uv run pyright
uv run pytest
pnpm run format # or npx prettier --write .
pnpm run lint # or npx eslint .
pnpm run typecheck # or npx tsc --noEmit
pnpm test
cargo fmt
cargo clippy
cargo test
gofmt -w .
go vet ./...
go test ./...
# Priority order
if [ -f "Makefile" ]; then
# Check for make validate/format/lint/test targets
elif [ -f "pyproject.toml" ]; then
# Python -- check for uv, poetry
elif [ -f "package.json" ]; then
# Node.js -- check for pnpm, npm, yarn
elif [ -f "Cargo.toml" ]; then
# Rust
elif [ -f "go.mod" ]; then
# Go
fi
Cache discovered validation info in the project's CLAUDE.md:
## Project Validation Tools
- **Format**: make format
- **Lint**: make lint
- **Type Check**: make typecheck
- **Test**: make test
Read ~/.claude/references/status-marks.md and follow its conventions. Report one line per check, then a single plain-text summary line.
Example output:
❨`✓`❩ Trim trailing whitespace
❨`✓`❩ Fix end of file markers
❨`~`❩ Mixed line endings (skipped — none found)
❨`✗`❩ Markdownlint (3 errors)
After the list, add a plain-text summary with no marks — e.g. "all checks passed" or "1 failure: markdownlint". Skip reasons go in parens on the same line. Never collapse the per-item list into a single emoji'd summary.