kiro-review
Run Kiro CLI as an independent reviewer over the current branch, a specific commit, or uncommitted changes. Builds a focused prompt from the real diff and returns a compact review summary.
What this skill does
<EXTREMELY-IMPORTANT> This skill orchestrates an external reviewer and must stay disciplined. Non-negotiable rules: 1. Read the real diff before writing the Kiro prompt. 2. Make the prompt specific to the changed areas and likely risks. 3. Never put secrets or credentials in the prompt. 4. Carry forward exclusion lists on later rounds. 5. Verify returned findings before acting on them. </EXTREMELY-IMPORTANT> # Kiro Review ## Inputs - `$request`: Optional scope hint such as `last commit`, `uncommitted`, `auth focus`, or `round 2` ## Goal Use `kiro-cli` to get an external review pass that: - uses the right diff scope - focuses on the actual change surface - returns structured findings instead of generic commentary ## Step 0: Verify Kiro availability Check: - `which kiro-cli` - `kiro-cli whoami` or the minimal auth check needed in this environment If the CLI is unavailable or not authenticated, explain the blocker and stop. **Success criteria**: Kiro can run successfully from the current repository. ## Step 1: Resolve review scope Determine whether to review: - the full branch - uncommitted changes - a specific commit Read the diff summary and changed-file list first. If there is nothing to review, stop and say so explicitly. **Success criteria**: The review target is explicit and backed by a real diff. ## Step 2: Build the focused Kiro prompt Create a compact prompt that includes: - what changed - the major risk areas - any previously fixed issues to exclude on later rounds - an instruction to verify findings against the actual code - the expected compact output format Avoid generic prompts. They produce weak results. **Success criteria**: The prompt is specific to the change set rather than reusable boilerplate. ## Step 3: Run Kiro in non-interactive mode Invoke `kiro-cli chat` with: - `--no-interactive` -- runs without expecting user input, returns output directly - `-a` (trust all tools) -- kiro needs file read access to verify findings against source Always capture stderr with `2>&1` (kiro logs to stderr). Optional flags: - `--model <model>` -- specify a particular model if needed - `--agent <agent>` -- use a specific agent profile for the review If the run is likely to take a while, background execution is acceptable, but keep the scope tight enough that the review stays focused. **Success criteria**: Kiro runs on the intended scope and returns parseable findings. ## Step 4: Summarize findings Report: - review scope - findings by priority - file and line references when available - explicit clean result when no material findings are returned If the user wants fixes, verify each finding locally before changing code. **Success criteria**: The user gets a readable review summary instead of raw CLI logs. ## Step 5: Iterate only with exclusions On later rounds: - list prior fixed findings in the exclusion block - narrow the scope to newly changed files when possible - avoid repeated full-branch reviews unless the code changed broadly again **Success criteria**: Follow-up rounds target new issues instead of recycling old ones. ## Guardrails - Do not run this skill proactively. - Do not put secrets, tokens, or private config into the prompt. - Do not trust findings blindly without local verification. - Do not skip diff reading before prompt construction. ## Output Contract Report: 1. the review scope 2. the main focus areas given to Kiro 3. findings by priority with locations when available 4. explicit clean result if nothing material was found 5. whether a next round should exclude previously fixed issues
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.