makefile-update
Makefile development workflow. Use when modifying Makefile or files in make/ directory.
Best use case
makefile-update is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Makefile development workflow. Use when modifying Makefile or files in make/ directory.
Teams using makefile-update should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/makefile-update/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How makefile-update Compares
| Feature / Agent | makefile-update | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Makefile development workflow. Use when modifying Makefile or files in make/ directory.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Makefile Workflow
Workflow for Makefile changes.
## Prerequisites
**Use `git-workflow` Skill** for branch, commit, and PR workflow.
## Applicable Files
| Path | Description |
|------|-------------|
| `Makefile` | Main makefile |
| `make/*.mk` | Included makefiles |
## Structure
```
Makefile # Main entry point, includes make/*.mk
make/
├── go.mk # Go-related targets
├── docker.mk # Docker targets
├── atlas.mk # Database migration targets
├── sqlc.mk # SQLC generation targets
└── ...
```
## Verification Commands
```bash
make mk-lint # Lint makefiles
```
### Manual Checks
```bash
# List all targets
make help
# Dry run (if supported)
make -n {target}
```
## Guidelines
### Style
- Use tabs for indentation (required by Make)
- Use `.PHONY` for non-file targets
- Add help text for targets
- Group related targets
### Best Practices
- [ ] Targets are `.PHONY` if not creating files
- [ ] Dependencies are correct
- [ ] Variables use `?=` for defaults
- [ ] Help text exists for main targets
### Example Target
```makefile
.PHONY: my-target
my-target: ## Description of target
@echo "Running my-target..."
command1
command2
```
## Verification Checklist
- [ ] `make mk-lint` passes
- [ ] Target runs correctly
- [ ] Dependencies work
- [ ] Help text is accurate
## Commit Format
```
chore(make): {brief description}
- {change 1}
- {change 2}
Closes #{issue_number}
```
## Related Skills
- `git-workflow` - Branch, commit, PR workflowRelated Skills
docs-update
Documentation update workflow. Use when modifying files in docs/ directory or any markdown files (*.md).
wallet-cli
How to run watch, keygen, and sign wallet CLI commands. Use when executing wallet commands or testing wallet functionality.
typescript-development
TypeScript/JavaScript development workflow for apps/ directory. Use when modifying TypeScript code in xrpl-grpc-server or JavaScript in eth-contracts.
solidity-development
Solidity smart contract development workflow. Use when modifying smart contracts in apps/eth-contracts/contracts/.
shell-scripts
Shell script development workflow. Use when modifying files in scripts/ directory or any *.sh files.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
mockery
Mock generation workflow for go-crypto-wallet. Activate whenever a developer asks to generate a mock for a new interface, add test coverage that requires a mock, or replace a manually-written test stub for a ports interface. Claude MUST use `make mockery` — never write mock struct code by hand.
label-context-mapping
Maps GitHub labels to Skills and Context documents. Use when creating issues (github-issue-creation) or working on issues (fix-issue command).
knowledge-gap
Post-task knowledge gap review and proposals for improving skills/rules