commit pi sessions
This commit is contained in:
@@ -1,3 +1,22 @@
|
||||
Review the current diff (`git diff`) as a senior engineer. Focus on:
|
||||
correctness, security, error handling, naming, and missing tests. Output a
|
||||
bullet list of issues with file:line references. Don't fix them — just list.
|
||||
---
|
||||
description: Review code, diffs, or changes with actionable feedback
|
||||
argument-hint: "[target: file path, diff, or PR]"
|
||||
subagent: true
|
||||
fork: true
|
||||
---
|
||||
Review the following code or changes: $@
|
||||
|
||||
Provide feedback in these categories:
|
||||
- **Correctness** — bugs, logic errors, edge cases, race conditions
|
||||
- **Security** — injection, unsafe defaults, secrets, auth/z issues
|
||||
- **Performance** — unnecessary work, memory leaks, hot-path inefficiencies
|
||||
- **Maintainability** — naming, complexity, duplication, testability
|
||||
- **Style & Idioms** — consistency with the surrounding codebase
|
||||
- **Error Handling** — missing or misleading failure modes
|
||||
|
||||
For each issue, include:
|
||||
- The specific location (file, line, function)
|
||||
- A clear description of the problem
|
||||
- A concrete suggestion or example fix
|
||||
|
||||
Also call out anything done well. Keep the review concise and prioritized.
|
||||
Reference in New Issue
Block a user