reviewable-diff-discipline

Stage explicit paths and verify staged diffs match declared intent.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill reviewable-diff-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewable-diff-discipline
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/reviewable-diff-discipline
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill reviewable-diff-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents scope drift, accidental file staging, and noisy commits by keeping every change tightly aligned to the declared intent.

Core Features & Use Cases

  • Intent-scoped editing: Work only on the files required by the task and record unrelated discoveries instead of fixing them inline.
  • Exact-path staging: Stage files explicitly and verify the staged set matches the intended file list before committing.
  • Diff hygiene checks: Inspect the working tree for generated artifacts, secrets, backup files, or unexpected churn before finalizing a PR.
  • Use case: When a small bug fix is buried in a dirty branch with unrelated WIP, this Skill helps produce a minimal, human-reviewable commit.

Quick Start

Use the reviewable-diff-discipline skill to keep this change limited to the declared files, stage only those paths, and confirm the staged diff matches the intent before committing.

Frequently Asked Questions about reviewable-diff-discipline

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

FAQPage Schema
How do I keep my git commit diff small and scoped to only the intended changes?

Keep your git commit diff small by explicitly staging exact file paths and verifying the staged set matches your stated intent before finalizing. Record unrelated discoveries separately instead of fixing them inline to prevent scope drift.

What is diff hygiene and why does it matter for pull requests?

Diff hygiene is the practice of inspecting your working tree for generated artifacts, secrets, backup files, or unexpected churn before finalizing a pull request. It ensures your staged changes remain minimal, exact, and human-reviewable.

How do I stage specific files in a dirty git branch without including unrelated WIP?

Stage specific files in a dirty git branch by using explicit-path staging to add only the required files. Verify the staged diff matches your intended file list exactly to ensure unrelated work-in-progress stays out of the commit.

Can I use this approach to clean up a mixed repository before preparing a pull request?

Yes, you can use this approach in mixed or dirty repositories to prepare a pull request. It applies intent-scoped editing, exact-path staging, and hygiene checks to isolate minimal, reviewable commits from surrounding unrelated changes.

What should I check for before finalizing a pull request to prevent sensitive data leaks?

Before finalizing a pull request, check your working tree for secrets, generated artifacts, and backup files. Running diff hygiene checks prevents accidental staging of sensitive data and keeps the commit focused on its declared intent.