About compare-files
A skill for comparing two files and reporting their differences. It is intended for requests that need a concrete file comparison rather than planning or high-level discussion.
Key features
- 01Compare two files
- 02Show differences
- 03Return task-specific findings and action notes
Use cases
- 01Identify changes between two file versions
- 02Review differences before applying edits
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/compare-filesin Claude Code to confirm it loaded.
Details
From the project READMECompare Files
Purpose
Compare two files and show differences
Routing
- Use when: Use when the user asks to compare two files and show differences.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from Compare Files: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
- Use the compare-files skill for this request.
- Help me with compare files.
- Use when the user asks to compare two files and show differences.
- Compare Files: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use compare-files for unrelated requests.
- This request is outside compare files scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| file1 | string | Yes | Path to the first file |
| file2 | string | Yes | Path to the second file |
Runtime Prompt
- Current runtime prompt length: 477 characters.
- Runtime prompt is defined directly in
../compare-files.json.
Comments
Markdown supported