Files

Added three issue templates to improve issue tracking:
- Feature request template for new features and enhancements.
- Bug report template for reporting bugs and unexpected behavior.
- General issue template for issues that don't fit other categories.

Templates follow Gitea best practices with proper frontmatter metadata.
Each template includes clear sections with inline comments to guide users.

Updated CLAUDE.md with issue management and workflow documentation.

Closes #21

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2026-01-12 20:40:25 -05:00

2.3 KiB

Raw Blame History

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.

Issue Management

Use the tea CLI (Gitea command-line tool) for issue operations.

Common commands:

tea issues list - List all issues.
tea issues <number> - View details of a specific issue.
tea issues create --title "<title>" --body "<description>" - Create a new issue.
tea issues close <number> - Close an issue.

Reading issues: Use tea issues <number> to read the full details of an issue before starting work.

Issue Workflow

When working on an issue:

Read the issue using tea issues <number> to understand requirements.
Create a feature branch following the branch naming convention.
Make commits following the conventional commit format.
Submit a pull request when ready.

Important: Never commit directly to main. All work must be done in a feature branch and submitted via pull request.

Pull Request Management

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