Add CLAUDE.md with comprehensive project guidelines including: - Conventional commit format and types - Branch naming conventions - PR management using tea CLI Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
Guide To lambda
Absolutely NO advertisement of Claude.
Coding Styles
Conventional Commits
Use conventional commit format: <type>: <description>.
Types: feat, fix, docs, refactor, test, chore, perf
Examples:
feat: add explanation mode flag to CLIfix: correct variable renaming in nested abstractionsdocs: update Makefile documentation
Branch Names
Use format: <type>/<description> with kebab-case.
Types: Same as commits: feat, fix, docs, refactor, test, chore, perf.
Examples:
feat/explanation-modefix/variable-renamingdocs/makefile-improvementsrefactor/silent-directive
Pull Request Management
Use the tea CLI (Gitea command-line tool) for PR operations instead of gh.
Common commands:
tea pr create- Create a new pull request.tea pr list- List pull requests.tea pr checkout <number>- Check out a PR locally.tea pr close <number>- Close a pull request.tea pr merge <number>- Merge a pull request.
Creating PRs: Always create PRs in a branch other than main, to the main branch unless specified otherwise.