name	code-review
description	Review code for correctness, style, and potential bugs

Follow these steps when reviewing code:

Read the whole file first before commenting. Understand the purpose and context before judging individual lines.
Check for null / undefined access — look for .property on values that could be null/undefined. In TypeScript, check that types match and optional chaining is used where needed.
Verify error handling — every await call and file I/O operation should have a try/catch or propagate the error up. Swallowed errors (catch {}) should be flagged.
Check that async functions are awaited — a common bug is calling an async function without await and discarding the returned Promise.
Look for resource leaks — file handles, streams, and connections should be closed in a finally block or use using / defer patterns.
Review naming — variable and function names should describe what the thing is or does. Single-letter names outside of loop indices should be flagged.
Check test coverage — for each exported function, there should be at least one test for the happy path and one for error conditions.
Flag magic numbers and strings — literal values like 3, "active", or 86400 should be named constants.
Report findings as a structured list: one line per issue, with the format [severity] file:line — description. Severity: error (breaks), warning (risky), suggestion (style).
End with a summary: total counts per severity and an overall verdict (approve / request changes).

name	code-review
description	Review code for correctness, style, and potential bugs

Follow these steps when reviewing code:

Read the whole file first before commenting. Understand the purpose and context before judging individual lines.
Check for null / undefined access — look for .property on values that could be null/undefined. In TypeScript, check that types match and optional chaining is used where needed.
Verify error handling — every await call and file I/O operation should have a try/catch or propagate the error up. Swallowed errors (catch {}) should be flagged.
Check that async functions are awaited — a common bug is calling an async function without await and discarding the returned Promise.
Look for resource leaks — file handles, streams, and connections should be closed in a finally block or use using / defer patterns.
Review naming — variable and function names should describe what the thing is or does. Single-letter names outside of loop indices should be flagged.
Check test coverage — for each exported function, there should be at least one test for the happy path and one for error conditions.
Flag magic numbers and strings — literal values like 3, "active", or 86400 should be named constants.
Report findings as a structured list: one line per issue, with the format [severity] file:line — description. Severity: error (breaks), warning (risky), suggestion (style).
End with a summary: total counts per severity and an overall verdict (approve / request changes).

code-review

このリポジトリの他の Skills