Analyze and enhance Makefiles for complete user functionality coverage. Triggers: Makefile analysis, Makefile gaps, missing targets, plugin release, Makefile coverage, build targets, make dogfood, plugin quality Use when: analyzing Makefile completeness before releasing plugins, identifying gaps during plugin maintenance, scoring Makefiles against best practices, verifying Makefiles support standard developer workflows DO NOT use when: writing initial Makefiles from scratch. DO NOT use when: debugging specific build target failures. DO NOT use when: creating custom non-standard build systems. Use this skill BEFORE releasing any plugin to verify Makefile coverage.
/plugin marketplace add athola/claude-night-market/plugin install abstract@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/analysis.mdmodules/generation.mdmodules/testing.mdAnalyzes Makefiles to identify gaps in user-facing functionality, safely tests existing targets, and generates missing targets with contextually appropriate templates.
This skill provides comprehensive Makefile analysis and enhancement for the claude-night-market project. It helps ensure that all plugins have complete, consistent, and functional Makefile targets that support common user workflows.
# Find all Makefiles and extract targets
makefile_dogfooder.py --scope all --mode analyze
The discovery phase:
# Analyze against best practices
makefile_dogfooder.py --mode analyze --output json
The analysis phase evaluates:
# Safely test existing targets
makefile_dogfooder.py --mode test
The testing phase performs:
make -n# Generate missing targets
makefile_dogfooder.py --mode full --apply
The generation phase creates:
File: modules/discovery.md
File: modules/analysis.md
File: modules/testing.md
File: modules/generation.md
makefile_dogfooder.py --plugin abstract --mode analyze
makefile_dogfooder.py --scope plugins --mode test
makefile_dogfooder.py --mode full --apply --output json
makefile_dogfooder.py --scope root --mode analyze
Human-readable summary with scores and recommendations:
=== Makefile Dogfooding Results ===
Scope: all
Mode: full
Makefiles analyzed: 10
Issues found: 23
Recommendations made: 15
Machine-readable results for automation:
{
"scope": "all",
"mode": "full",
"makefiles_analyzed": 10,
"details": [
{
"file": "plugins/abstract/Makefile",
"score": 100,
"issues": 0,
"recommendations": 0
}
]
}
## commentThe skill integrates with the /make-dogfood slash command for easy access:
/make-dogfood --scope plugins --mode full
Include in GitHub Actions for automated Makefile validation:
- name: Validate Makefiles
run: makefile_dogfooder.py --mode test --output json
Run as part of pre-commit hooks:
- repo: local
hooks:
- id: makefile-dogfooding
entry: makefile_dogfooder.py
language: system
args: [--mode, analyze]
--scope to limit analysis scope--mode analyze for fastest feedback--mode test without --apply for safe validation--mode analyze instead of --mode test for slow targetsEnable verbose output for troubleshooting:
makefile_dogfooder.py --mode analyze --output json | jq '.details[] | select(.issues > 0)'
To extend the skill:
MIT License - see LICENSE file for details.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.