review-scope

Name: review-scope
Availability: InStock
Author: dannys-code-corner

Review cross-file changes against issue, RFC, and branch scope.

92|7|Updated Dec 11, 2025

Search Tags:#review #scope #change-management #issue-rfc #branch-intent #slice-report

Ready to run

npx skills add https://github.com/dannys-code-corner/incan --skill review-scope-dannys-code-corner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-scope
Source: https://github.com/dannys-code-corner/incan/tree/main/.agents/skills/review-scope
Command: npx skills add https://github.com/dannys-code-corner/incan --skill review-scope-dannys-code-corner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a focused, cross-file review to verify that a change aligns with the associated issue, RFC, branch intent, and user-request scope, helping teams identify missing coverage, scope creep, or mismatches before merging.

Core Features & Use Cases

Cross-file scope verification against issue/RFC/branch intent and user expectations.
Generates a dedicated scope slice report at .agents/state/review-report.scope.md.
Flags missing in-scope work, scope creep, or scaffolds that imply unsupported flows.

Quick Start

Run a scope review on the current worktree to produce the slice report at .agents/state/review-report.scope.md.

Frequently Asked Questions about review-scope

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

FAQPage Schema

How do I verify my branch changes match the original issue and RFC scope?▼

To verify branch changes match the issue and RFC scope, perform a cross-file scope review across the worktree to check for alignment with defined intent and user expectations, ensuring the implementation matches the defined scope before merging.

What does a scope review check for in a feature branch?▼

A scope review checks feature branches for missing in-scope work, scope creep, and unsupported scaffolds. It compares the worktree changes against the issue, RFC, and branch intent to ensure the implementation fully matches the defined scope.

How can I detect scope creep before merging a proposal?▼

You can detect scope creep before merging a proposal by running a cross-file scope review. It identifies unsupported scaffolds and mismatched work by verifying the worktree against the defined RFC and branch intent, ensuring changes remain on-target.

Where does the scope slice report get saved after a review?▼

The scope slice report gets saved directly at .agents/state/review-report.scope.md. This dedicated review artifact captures the cross-file findings, including missing in-scope work and scope creep, for later analysis and team visibility.

Do I need any dependencies to run a cross-file scope review?▼

No dependencies are required to run a cross-file scope review. The process operates independently across the repository worktree to verify changes against the issue, RFC, and branch intent, generating the slice report without external tools.