Thank you for your interest in contributing to agent-config!
- Report bugs or unexpected behavior
- Suggest new skills, commands, or subagent configurations
- Improve documentation
- Submit fixes or new features via pull request
- Fork the repository
- Clone your fork:
git clone https://github.com/<your-username>/agent-config.git - Create a branch from
main:git checkout -b <type>/<short-description> - Make your changes
- Test that symlinks and configurations work correctly:
make all - Submit a pull request
Use the format <type>/<short-description>, where type is one of:
feat- new skill, command, subagent, or capabilityfix- bug fixdocs- documentation onlychore- maintenance, tooling, scriptsrefactor- restructuring without behavior change
This project uses Conventional Commits:
<type>(<scope>): <short summary>
<optional body explaining why, not what>
- type:
feat,fix,docs,chore,refactor,style,ci,test - scope: the directory or component affected (e.g.,
skills,commands,agents/claude,scripts) - summary: imperative mood, lowercase, no trailing period, max 72 characters
- Keep PRs focused — one logical change per PR
- Update relevant README files if your change affects documented behavior
- Ensure
make allruns without errors before submitting - Fill out the pull request template
| Resource type | Location | Notes |
|---|---|---|
| Skills | skills/<name>/ |
Include a SKILL.md |
| Commands | commands/<name>.md |
Follow existing frontmatter format |
| Subagents | subagents/<name>/ |
Include agent instructions |
| Agent configs | agents/<agent>/ |
Edit _<AGENT>.md; run make generate |
| Prompts | prompts/ |
Document in prompts/README.md |
Not all resources work with all agents. If your contribution is agent-specific, note that clearly in the relevant files.
Please open an issue and use the appropriate issue template.