Thanks for your interest in contributing! This document outlines how to get involved.
- Fork the repository on GitHub
- Clone your fork locally:
git clone git@github.com:YOUR-USERNAME/dotfiles-claude.git ~/.claude - Create a branch for your changes:
git checkout -b feature/your-feature-name
- Use British English spelling (behaviour, colour, organisation)
- Follow existing patterns in the codebase
- Keep commits atomic and focused
Follow Conventional Commits:
feat:— New featurefix:— Bug fixdocs:— Documentation onlyrefactor:— Code change that neither fixes nor addschore:— Maintenance tasks
Example:
feat: add new-project-phoenix skill
Automates Phoenix/Elixir project creation with personal conventions.
Before submitting:
- Ensure skills work as expected by invoking them
- Check that documentation is accurate
- Verify no sensitive data is included
-
Push your branch to your fork:
git push origin feature/your-feature-name
-
Open a Pull Request against the
masterbranch -
Describe your changes clearly:
- What does this PR do?
- Why is this change needed?
- Any breaking changes?
Found a bug or have a suggestion? Open an issue with:
- Clear description of the problem or suggestion
- Steps to reproduce (for bugs)
- Expected vs actual behaviour
- Your environment (OS, Claude Code version)
Ideas for contributions:
- New skills — Automate common workflows
- Bug fixes — Fix issues in existing skills/commands
- Documentation — Improve clarity, fix typos, add examples
- Playbooks — Document useful procedures
Open an issue for discussion before starting large changes. This helps ensure your contribution aligns with the project direction.