continue-rebase-interactively
Guide an in-progress rebase with conflicts by summarizing each conflict and offering 3 resolution options.
Script and automate repetitive tasks and workflows.
Guide an in-progress rebase with conflicts by summarizing each conflict and offering 3 resolution options.
Generate CodMate slash command drafts from requirements.
Help users build software using AI coding tools. Use when someone is using AI to generate code, building prototypes without deep technical skills, or exploring how non-engineers can create functional software through natural language.
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
Use when working with code refactoring context restore
Regenerate all generated code from .synq definitions and SQLite grammar. Use when .synq files, grammar actions, or dialect definitions have been modified and generated C/Rust code needs updating.
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, build tooling (tsdown/unbuild), API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, configuring dual CJS/ESM output, or setting up release workflows.
Refactoring assessment and patterns. Use after mutation testing validates test strength (MUTATE phase) to assess improvement opportunities.
Create comprehensive steering documents for development projects. Generates project-specific standards, git workflows, and technology guidelines in .kiro/steering/ directory.
Review blade PRs by fetching diff, checking CI status, and getting Storybook URL. Use when reviewing PRs, checking PR status, or getting preview links for razorpay/blade PRs.
Generate bi-weekly announcement posts for Blade Design System updates by analyzing changelog entries from the past two weeks
Automated iterative code review and fix loop with parallel review agents
Google Gemini CLI code review with Gemini 2.5 Pro, 1M token context, CI/CD integration
Mandatory code reviews via /code-review before commits and deploys
Analyze existing repositories, maintain structure, setup guardrails and best practices
Prevent semantic code duplication with capability index and check-before-write
Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.
Generate and update CHANGELOG.md for a new kubelogin release. Use this when asked to prepare release notes or update the changelog for a new version. Fetches merged pull requests since the previous release, categorizes them, identifies new contributors, and prepares a formatted entry for CHANGELOG.md.