detect-kiro-specs

Detect modified Kiro specs in the current branch using git diff.

Updated Dec 6, 2025
One-click install
npx skills add https://github.com/reedom/claude-code-commands --skill detect-kiro-specs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-kiro-specs
Source: https://github.com/reedom/claude-code-commands/tree/main/kiro-detect-specs/skills
Command: npx skills add https://github.com/reedom/claude-code-commands --skill detect-kiro-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detects which Kiro specs have been affected by changes in the current branch to guide targeted testing.

Core Features & Use Cases

  • Scans .kiro/specs and diff to find modified specs
  • Outputs a clean list of spec names, sorted uniquely

Quick Start

Run ./scripts/main.sh to emit the list of modified specs for your current branch.

Frequently Asked Questions about detect-kiro-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect which Kiro specs have changed in my branch?

Detecting modified Kiro specs identifies which specs are affected by your branch changes. Run ./scripts/main.sh to scan your .kiro/specs directory against git diff, which outputs a sorted list of modified spec names for targeted testing.

When should I use spec detection before a pull request?

Spec detection before pull requests filters which specs need testing by identifying only the ones your changes affect. This reduces CI time and testing scope by running only relevant spec tests instead of the full suite.

What directory structure does spec detection require?

Spec detection requires a .kiro/specs directory organized into subdirectories, one per spec. The tool matches modified file paths against these subdirectories to determine which specs changed.

Can I use spec detection to filter CI test runs?

Yes, spec detection outputs a clean, sorted list of modified spec names that CI pipelines can consume to run only affected specs. This guides conditional testing and reduces pipeline execution time.

How does the tool handle multiple modified specs?

The tool scans git diff against all subdirectories in .kiro/specs, collects matches, deduplicates them, and outputs a single alphabetically sorted list of distinct modified spec names for downstream use.