collect-commits-and-files

Collect and categorize changed files from Git for review workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Reviewers waste time parsing changed files. This Skill classifies diffs into sources, tests, docs, and configs to speed up reviews.

Core Features & Use Cases

  • Diff collection against target branch plus explicit files
  • Categorization into source, test, config, docs
  • Output manifest guiding downstream review agents

Quick Start

Run the collect-info.sh with --against origin/main and optional --files paths to generate the manifest.

Frequently Asked Questions about collect-commits-and-files

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

FAQPage Schema
How do I organize changed files by category for code review?

Collect changed files from git diff and categorize them into source, test, config, and docs groups. This Skill classifies diffs against a target branch into a structured manifest, generating per-file diffs and category-based file lists to streamline focused code reviews.

Can I automate diff collection against a specific branch?

Yes. Run collect-info.sh with --against origin/main to collect diffs against your target branch, plus optional --files paths to include explicit files. The Skill outputs a JSON manifest with categorized file lists and per-file diffs for downstream review workflows.

What output does diff classification produce for review workflows?

Diff classification generates a JSON manifest containing temp_dir, repo_root, against_branch, categorized file paths (source, test, config, docs), per-file diffs stored as .diff files, and a summary. This manifest guides downstream review agents through organized file triage.

How does this handle errors when collecting diffs?

The Skill detects and reports NOT_GIT_REPO, BRANCH_NOT_FOUND, NO_FILES, and NO_EXISTING_FILES errors. It validates the git repository, target branch existence, and file availability before generating the manifest, preventing partial or invalid reviews.

What's the difference between diffing and file categorization in code review?

Diffing shows what changed in each file; categorization groups those files by type (source, test, config, docs). This Skill combines both—it collects diffs and organizes files by category—so reviewers focus on one type at a time instead of parsing a flat changelist.

Do I need explicit file paths, or does git diff suffice?

Git diff is sufficient to collect changes against your target branch. Optional --files paths let you include additional files outside the diff scope. The Skill accepts both, merging them into one categorized manifest for flexible review coverage.