Thank you for your interest in contributing. This document outlines the process and standards for contributing.
- Fork the repository and clone your fork
- Create a branch from
main:git checkout -b feat/your-featureorfix/your-fix - Make changes following our commit conventions
- Open a Pull Request targeting
main
All changes to main must go through a Pull Request. Direct pushes to main are not allowed.
We use Conventional Commits. Each commit must follow:
<type>(<scope>): <description>
| Type | Use for | Version impact |
|---|---|---|
feat |
New features | Minor bump |
fix |
Bug fixes | Patch bump |
docs |
Documentation only | No bump |
style |
Formatting, no code change | No bump |
refactor |
Code restructure | No bump |
perf |
Performance improvements | Patch bump |
test |
Adding tests | No bump |
ci |
CI/CD changes | No bump |
chore |
Maintenance | No bump |
Use one of: skill, commands, environments, troubleshooting, workflows, deps, release, config
feat(commands): add database backup workflow
fix(troubleshooting): correct Xdebug connection steps
docs(config): update README installation section
ci(config): add id-token permission for npm
For breaking changes, append ! after the type/scope or add BREAKING CHANGE: in the footer:
feat(skill)!: restructure SKILL.md format
Before merging, ensure:
- All commits follow Conventional Commits
- PR Checks workflow passes (commitlint, skill validation)
- SKILL.md remains under 500 lines
-
metadata.jsonandpackage.jsonare valid JSON
Releases are automated. When your PR is merged to main:
featcommits → minor version bump (1.0.0 → 1.1.0)fix/perfcommits → patch bump (1.0.0 → 1.0.1)feat!/BREAKING CHANGE→ major bump (1.0.0 → 2.0.0)
The workflow will publish to npm and create a GitHub Release automatically.
Open an Issue for questions or discussions.