Review code like a senior engineer (Kotlin)

Steps

1. 1Read description and tests FIRST to learn intent
2. 2Check correctness and security before style nits
3. 3Comment questions/observations vs required-changes distinctly
4. 4Keep nitpicks batched as one optional pass
5. 5Approve explicitly when remaining items are optional
6. 6Aim same-day first response; latency kills momentum
7. 7Leverage coroutines structured concurrency; cancel scopes deliberately
8. 8Watch Kotlin/Native memory model differences in multiplatform code

Common Pitfalls

• ▲Style wars the formatter should own
• ▲LGTM rubber-stamps on 2000-line diffs

Commands

$ npx skills add aniruddhaadak80/skills --skill code-quality-code-review-checklist-kotlin

$ npx skills add aniruddhaadak80/skills --skill code-quality-code-review-checklist-kotlin -g

Tags