scope-resolver

Resolve scope specifications into complete Scope Bundles for review agents.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/donygeorge/claude-toolkit --skill scope-resolver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-resolver
Source: https://github.com/donygeorge/claude-toolkit/tree/main/skills/scope-resolver
Command: npx skills add https://github.com/donygeorge/claude-toolkit --skill scope-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolves user intent into a concrete Scope Bundle for review agents, ensuring consistent scope definitions across features, uncommitted changes, and diffs.

Core Features & Use Cases

  • Resolve feature scopes, uncommitted changes, and diff ranges into a single, machine-readable Scope Bundle that includes scope_key, scope_slug, scope_type, commit_hash, files, diff, language_breakdown, risk_profile, tests_touched, likely_tests_missing, and entrypoints.
  • Validate scope mappings to avoid ambiguous results and provide deterministic outputs for downstream review tools.
  • Integrate with project configurations like features.json to map features to files and entrypoints for automated review workflows.

Quick Start

Invoke the scope-resolver with a scope specification (for example feature:my-feature or uncommitted) to generate a complete Scope Bundle for reviewer agents.

Frequently Asked Questions about scope-resolver

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

FAQPage Schema
How do I resolve feature scopes and uncommitted changes into a review bundle?

Resolving feature scopes and uncommitted changes into a review bundle involves mapping user-provided scope specifications into a complete Scope Bundle containing files, diffs, language_breakdown, risk_profile, tests_touched, and entrypoints for downstream review workflows.

What is a Scope Bundle in code review automation?

A Scope Bundle in code review automation is a machine-readable output package that standardizes scope definitions across features, uncommitted changes, and diff ranges, providing deterministic outputs including commit_hash, risk_profile, and entrypoints for reviewer agents.

How do I map feature names to files and entrypoints for automated code review?

Mapping feature names to files and entrypoints for automated code review is done by integrating with project configurations like features.json, which validates scope mappings to avoid ambiguous results and generates deterministic outputs for automated workflows.

Does scope resolution work with diff ranges and uncommitted changes?

Scope resolution works with diff ranges and uncommitted changes by accepting varied scope specifications like feature:my-feature or uncommitted, validating the mappings to avoid ambiguity, and generating a full bundle with diffs and risk profiles.

Why does scope resolution enforce strict output formatting for review agents?

Scope resolution enforces strict output formatting to ensure consistent scope definitions and provide deterministic, machine-readable Scope Bundles that downstream review agents can reliably parse without encountering ambiguous results.