Thanks for your interest in contributing! Lean Loop is a lightweight methodology — contributions should keep it simple.
- Use GitHub Issues for bugs, feature requests, and questions
- Check existing issues before creating a new one
- Include steps to reproduce for bug reports
- Fork the repository
- Create a feature branch:
git checkout -b my-improvement - Make your changes
- Test that the skill installs and initializes correctly:
npx skills add ./skills/lean-loop -g - Submit a pull request
Welcome:
- Template improvements (better structure, clearer language)
- Documentation fixes and clarifications
- New examples in
examples/ - Translations of README
- Anti-pattern additions to SKILL.md
Discuss first (open an issue):
- Changes to the core PLAN → APPLY → UNIFY cycle
- New phases or sub-phases
- Changes to TDD_RULES.md templates
- Adding dependencies or tooling
- Keep it simple. Lean Loop's value is in its minimalism.
- Markdown files: use consistent heading levels and formatting
- Templates: keep emoji/formatting consistent with existing files
- No code — this is a methodology, not a framework
- Changes are minimal and focused
- README updated if behavior changes
- Templates updated if structure changes
- No breaking changes to existing
.system/file formats
By contributing, you agree your contributions will be licensed under the MIT License.