detect-repo-changes

Aggregate git commits, uncommitted changes, and agent knowledge to list changed files.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/notwillk/skills --skill detect-repo-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-repo-changes
Source: https://github.com/notwillk/skills/tree/main/skills/detect-repo-changes
Command: npx skills add https://github.com/notwillk/skills --skill detect-repo-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detect changes in a repository by applying a cascade of detection methods to identify files that have been modified, added, or deleted, enabling tasks like version bumps, change logging, or selective testing.

Core Features & Use Cases

  • Cascade detection across git commits since branch point (if history exists), uncommitted changes, and agent knowledge to surface changed files
  • Output formats that present a concise list of changed files for automation or review
  • Use Case: Before a release, quickly determine what files changed to decide testing scope or bump strategy

Quick Start

Detect changes in the repository and return a concise list of modified, added, and deleted files.

Frequently Asked Questions about detect-repo-changes

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

FAQPage Schema
How do I detect repository changes for a version bump or change log?

You can detect repository changes by applying a cascade of detection methods that identify modified, added, or deleted files. This approach aggregates git commits, uncommitted changes, and agent knowledge to output a concise list of changed files for version bumps or change logging.

Can I detect file changes in a non-git repository?

Yes, you can detect file changes in a non-git repository. The detection mechanism is applicable in both git-enabled and git-less workflows, coordinating agent knowledge to assess the current workspace state when git history is unavailable.

What is the best way to identify modified, added, or deleted files before a release?

The best way to identify modified, added, or deleted files before a release is using a cascade detection method. It aggregates git commits since the branch point and uncommitted changes to surface changed files, helping you decide testing scope or bump strategy.

How does cascade detection work for uncommitted changes in git?

Cascade detection works by coordinating git-based detection across commits since the branch point alongside uncommitted changes and agent knowledge. This aggregation surfaces a comprehensive list of changed files in the current workspace for automation or review.

Do I need a git repository to track deleted or added files?

No, you do not need a git repository to track deleted or added files. The detection mechanism is designed for both git-enabled and git-less workflows, utilizing agent knowledge to assess workspace state and output changed files when git is absent.