nib

Review code changes for correctness, security, performance, and style. Use when the user wants a thorough review of a diff, PR, or specific files before merging or submitting.

Systematically debug an error, unexpected behavior, or failing test. Use when the user has a bug, crash, or test failure they need to diagnose and fix.

Generate or update documentation for an existing codebase. Use when the user needs a README, API reference, module-level docs, or inline code comments written or refreshed based on the actual code.

Generate a well-formatted Git commit message based on staged changes. Use when the user wants to commit code and needs a clear, conventional commit message written for them.

Break down a feature or project requirement into a structured development plan with tasks, milestones, and implementation order. Use when the user has a goal but needs to figure out what to build and in what sequence.

Refactor code to improve structure, readability, or performance without changing external behavior. Use when the user wants to clean up or restructure existing code safely.

Generate a new project skeleton from scratch based on the user's chosen tech stack. Use when starting a new project and needing the initial directory structure, config files, and boilerplate set up correctly.

Generate unit tests or integration tests for existing code. Use when the user wants test coverage for a function, module, or feature that currently has no tests or insufficient tests.