keen-code

Release a new version of the project.

Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.

Ask focused clarifying questions to resolve ambiguous requirements before planning or implementing work.

Explain code, behavior, architecture, or diffs with concrete references to the relevant files.

Diagnose failing tests, determine whether code or tests are wrong, and make the smallest passing fix.

Refactor existing code while preserving behavior, keeping changes scoped, and verifying with relevant tests.

Review current code changes for bugs, regressions, test gaps, and project-guideline violations.