huzaifa525

Use when the user wants a changelog, release notes, or asks what changed since the last release.

Use when the user wants to create a pull request, open a PR, or submit changes for review.

Use when the user has an error, bug, stack trace, failing test, or unexpected behavior to diagnose.

Use when the user wants a code review, quality check, or asks to review their changes.

Use when you need to understand a module, feature, or directory before making changes.

Use when the user wants to plan a feature, design an implementation approach, or break down a complex task before coding.

Use when a task requires 5+ steps, multiple file changes, or cross-session progress tracking. Auto-activates for complex multi-step work.

Use when the user wants a security audit, vulnerability scan, or asks about potential security issues.

Use when the user wants to set up Claude Code for a project, initialize optimization, or generate CLAUDE.md.

Use when the user wants to check dependencies, find outdated packages, or audit for vulnerabilities.

Use when the user wants to fix a GitHub issue by number, resolve a bug report, or close an issue.

Use when starting a new session, the project has changed significantly, or you need a fresh context summary.

Use when the user wants to change optimization aggressiveness, switch between aggressive/balanced/thorough modes, or adjust token-saving behavior.

Use when the user wants to refactor, clean up, restructure, or reorganize existing code without changing behavior.

Use when the user wants test-driven development, asks to write tests first, or mentions TDD.

Use when the user wants to add documentation, JSDoc, docstrings, or API docs to existing code.

Use when the user wants to migrate, upgrade, or move from one framework, library, or API version to another.

Use when a new developer needs to understand the project, or the user asks for an onboarding or setup guide.

Use when the user wants to reduce token costs, find savings opportunities, or optimize Claude Code usage.

Use when the user wants to check performance, find slow code, identify bottlenecks, or audit efficiency.

Use when adding new features or modifying existing code where following existing codebase patterns matters.

Use when executing a multi-task plan where each task is independent, or when the user wants parallel or isolated task execution with review.

Use when the user wants to work in an isolated branch, start a safe development environment, or avoid polluting the main branch.

Use when the user asks about token usage, session cost, or wants to check optimization effectiveness.

Úsalo cuando el usuario quiera confirmar cambios, guardar trabajo o crear un mensaje de commit de git.