claude-code-plugin-ref…
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops;…
Audits Makefiles for build correctness, portability, and recipe duplication. Use when reviewing a Makefile or before committing Makefile changes.
Claude Code
$ npx -y skills add athola/claude-night-market --skill makefile-review --agent claude-code
Codex
$ npx skills add athola/claude-night-market --skill makefile-review -a codex -y
Cursor
$ npx skills add athola/claude-night-market --skill makefile-review -a cursor -y
Gemini CLI
$ npx skills add athola/claude-night-market --skill makefile-review -a gemini-cli -y
GitHub Copilot
$ npx skills add athola/claude-night-market --skill makefile-review -a github-copilot -y
OpenCode
$ npx skills add athola/claude-night-market --skill makefile-review -a opencode -y
Windsurf
$ npx skills add athola/claude-night-market --skill makefile-review -a windsurf -y
name: makefile-review description: Audits Makefiles for build correctness, portability, and recipe duplication. Use when reviewing a Makefile or before committing Makefile changes. globs: "**/Makefile" alwaysApply: false category: build tags: - makefile - build - make - portability - automation tools: [] usage_patterns: - makefile-audit - build-optimization - portability-review - deduplication complexity: intermediate estimated_tokens: 150 progressive_loading: true dependencies: - imbue:proof-of-work - imbue:review-core - imbue:structured-output modules: - modules/dependency-graph.md - modules/deduplication-patterns.md - modules/portability-checks.md - modules/best-practices.md - modules/plugin-dogfood-checks.md
Run `pytest plugins/pensive/tests/skills/test_makefile_review.py` to verify review logic.
Audit Makefiles for best practices, deduplication, and portability.
/makefile-review
1. `makefile-review:context-mapped` 2. `makefile-review:dependency-graph` 3. `makefile-review:dedup-candidates` 4. `makefile-review:tooling-alignment` 5. `makefile-review:evidence-logged` 6. `makefile-review:findings-verified`
Confirm baseline:
pwd && git status -sb && git diff --stat
**Verification:** Run `git status` to confirm working tree state.
Find Make-related files:
rg -n "^include" -g'Makefile*' rg --files -g '*.mk'
Document changed targets, project goals, and tooling requirements.
@include modules/dependency-graph.md
@include modules/deduplication-patterns.md
@include modules/portability-checks.md
Use `imbue:proof-of-work` to record command outputs with file:line references.
Summarize findings:
Load additional context as needed:
**Best Practices & Examples**: `@include modules/best-practices.md`
**Plugin Dogfood Checks**: `@include modules/plugin-dogfood-checks.md` - Makefile completeness analysis, target generation, and dogfooding validation.
## Summary Makefile review findings ## Context - Files reviewed: [list] - Targets changed: [list] ## Dependency Analysis [graph and issues] ## Duplication Candidates ### [D1] Repeated command - Locations: [list] - Anchor: `verbatim source text at file:line` - Recommendation: [pattern rule] ## Portability Issues [cross-platform concerns] ## Missing Targets - [ ] help - [ ] format - [ ] lint ## Recommendation Approve / Approve with actions / Block
Write findings to `.review/findings.json`, run the citation verifier (`Skill(imbue:review-core)` Step 5), and drop or label `UNVERIFIED` any the verifier rejects.
by `citation_verifier.py` (exit `0`), or unverified findings were dropped or labeled `UNVERIFIED`
**No Makefile found** Ensure `Makefile` or `*.mk` files exist in the project root or specify paths explicitly.
**Include directives not resolved** Run `rg -n "^include" -g'Makefile*'` to trace include chains manually.
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops;…
States load-bearing decisions, invariants, and weak points. Use when judging a design change. Do not use for gating; use…
Rebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for daily…
Classify, gate, and review changes. Use when landing a PR, releasing, or amending rules. Do not use for failure triage; use…
Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for settled…
Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.