Menu
Always read Makefile before proposing commands [Makefile, build, test, docker, workflow]
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
Read files BEFORE asking questions. Inspect to assist, not just to plan [reading, inspection, context, workflow, collaborative editing]
Design First, Code Second - explore options before implementation
Assist with interactive git rebase [git, rebase, history, cleanup, squash, reorder]
Session retrospective following desk/retro.md [feedback, session review, improvement, workflow, validation]
Write semantic git commits following conventional format
Task closing protocol - documentation updates and completion tracking
| name | makefile-awareness |
| description | Always read Makefile before proposing commands [Makefile, build, test, docker, workflow] |
| license | MIT |
| compatibility | opencode |
| metadata | {"related":["desk/DEVELOPMENT.md"]} |
I enforce the "read Makefile first" rule before proposing any build, test, or deployment commands.
Full details: Read desk/DEVELOPMENT.md section "Makefile Awareness" for complete guide.
BEFORE proposing ANY command:
1. Check if Makefile exists
2. Read available targets
3. Use Makefile targets instead of raw commands
User: "How do I build this?"
Me: [reads Makefile]
Me: "Run `make docker-build` - it includes the setup dependency."
User: "How do I build this?"
Me: "Run docker-compose build"
[Makefile has `make docker-build` with dependencies]