Gud Boi
0134b94db0
Deats, - top-level `ai/README.md` w/ integration table, conventions, and links to PR #69 (origin) + issue #79 (tracking) - `ai/claude-code/README.md` covering all 5 skills (summary table) and full `/commit-msg` usage guide: invocation, `$ARGUMENTS`, output format/files, frontmatter reference, dynamic context explanation (this patch was generated in some part by [`claude-code`][claude-code-gh]) [claude-code-gh]: https://github.com/anthropics/claude-code |
||
|---|---|---|
| .. | ||
| claude-code | ||
| README.md | ||
README.md
AI Tooling Integrations
Documentation and usage guides for AI-assisted development tools integrated with this repo.
Each subdirectory corresponds to a specific AI tool or frontend and contains usage docs for the custom skills/prompts/workflows configured for it.
Originally introduced in PR #69; track new integration ideas and proposals in issue #79.
Integrations
| Tool | Directory | Status |
|---|---|---|
| Claude Code | claude-code/ |
active |
Adding a New Integration
Create a subdirectory named after the tool (use lowercase + hyphens), then add:
- A
README.mdcovering setup, available skills/commands, and usage examples - Any tool-specific config or prompt files
ai/
├── README.md # <- you are here
├── claude-code/
│ └── README.md
├── opencode/ # future
│ └── README.md
└── <your-tool>/
└── README.mdConventions
- Skill/command names use hyphen-case (
commit-msg, notcommit_msg) - Each integration doc should describe what the skill does, how to invoke it, and any output artifacts it produces
- Keep docs concise; link to the actual skill source files (under
.claude/skills/, etc.) rather than duplicating content