Files
lambda/CLAUDE.md
M.V. Hutz c0353c8e1f feat: add required name field to PR template (#7)
## Description

Gitea requires a `name` field in the frontmatter of pull request templates.
This PR adds the required `name: "Default Template"` field to fix the template validation error.
Additionally updates CLAUDE.md to reference the PR template format and use lowercase for PR title placeholder.

## Benefits

- The pull request template is now valid and will be properly loaded by Gitea.
- Users creating PRs will see the template automatically populated.
- CLAUDE.md now documents the PR template format for consistency.

## Checklist

- [x] Code follows conventional commit format.
- [x] Branch follows naming convention (`<type>/<description>`).
- [x] Tests pass (if applicable).
- [x] Documentation updated (if applicable).

Reviewed-on: #7
Co-authored-by: M.V. Hutz <git@maximhutz.me>
Co-committed-by: M.V. Hutz <git@maximhutz.me>
2026-01-10 22:54:43 +00:00

1.4 KiB

Guide To lambda

Documentation Style

Use full sentences. Every sentence gets its own line in Markdown. Every sentence ends in a period.

Coding Style

Conventional Commits

Use conventional commit format: <type>: <description>.

Types: feat, fix, docs, refactor, test, chore, perf

Examples:

  • feat: add explanation mode flag to CLI
  • fix: correct variable renaming in nested abstractions
  • docs: update Makefile documentation

DO NOT advertise Claude.

Branch Names

Use format: <type>/<description> with kebab-case.

Types: Same as commits: feat, fix, docs, refactor, test, chore, perf.

Examples:

  • feat/explanation-mode
  • fix/variable-renaming
  • docs/makefile-improvements
  • refactor/silent-directive

DO NOT advertise Claude.

Pull Request Management

Use the tea CLI (Gitea command-line tool) for PR operations instead of gh.

Common commands:

  • tea pr create --title "<title>" --description "<body>" - 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.

Note: Use --description (not --body) for PR body content.

Creating PRs: Always create PRs in a branch other than main, to the main branch unless specified otherwise. ALWAYS FOLLOW THE PR TEMPLATE, EXACTLY.