Borrowing it
Nothing to install: this file belongs to Caspian-Sun/claude-code-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Caspian-Sun/claude-code-workflow/main/.claude/skills/ext-changelog/SKILL.mdgit clone --depth 1 https://github.com/Caspian-Sun/claude-code-workflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/caspian-sun/claude-code-workflow/ext-changelog)<a href="https://agentmods.dev/skills/caspian-sun/claude-code-workflow/ext-changelog"><img src="https://agentmods.dev/badge/skills/caspian-sun/claude-code-workflow/ext-changelog.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00077 | $0.00893 |
| Opus 5 | $0.00039 | $0.00447 |
| Sonnet 5 | $0.00015 | $0.00179 |
| Haiku 4.5 | $0.00008 | $0.00089 |
Grade A, and why
ext-changelog scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ext-changelog — Change Impact Report
You are now a code change analyst. Generate a readable impact report for git changes in the specified file/directory over a specified time range.
Difference from /release
/release— oriented toward publishing; outputs a structured changelog for tags/releases/ext-changelog— oriented toward understanding; outputs a human-readable change narrative for weekly reports / handoffs / retrospectives
Execution Approach
Run git log through scripts; AI handles grouping and interpretation — do not let AI reconstruct commits from memory.
Step 1: Get the commit list
bash .claude/skills/ext-changelog/scripts/range-commits.sh [since] [scope] [author]
Parameters (all optional):
since— start date; defaults to7 days ago; also accepts2026-04-01scope— path scope; defaults to.(entire repo)author— author filter; defaults to empty (all authors)
Each output line: hash|date|author|subject
Step 2: Get changed file statistics
bash .claude/skills/ext-changelog/scripts/changed-files.sh [since] [scope]
Output: A/M/D status for each file + its module directory.
Step 3: AI aggregates by module
After reading the script output:
- Group by
workspace/src/features/<module>/prefix - Parse commit messages in
type(scope): descriptionformat - Link to references in
docs/prds//docs/tasks//docs/bug-reports/ - Identify risk areas:
- Large-scale changes (a single commit touching > 10 files)
- Cross-module changes (one commit spanning multiple features)
- Commit messages containing
WIP/TODO/FIXME - Feature commits not linked to any PRD or task
Output Format
# Change Report: 2026-04-10 → 2026-04-17
## Summary
This week the main work was completing the login module, fixing 3 bugs, and refactoring the auth logic.
## Breakdown by Module
### login (12 commits, 5 files added, 3 files modified)
- Added username/password login + remember-me feature
- Added login form component, auth hook, and API wrapper
- PRD: docs/prds/login.md
### auth (3 commits, 2 files modified)
- Refactor: extracted shared auth logic into useAuth hook
- Impact: used by both login and register modules
## Bug Fixes
- Fixed Dashboard blank screen (login token expiry not redirecting)
- Fixed remember-me token not extending its validity period
## Risk Areas
- register page has not been regression-tested since the auth module refactor
- 2 [pending confirmation] items remain in login.md PRD
## Stats
- Total commits: 18
- Files added: 7
- Files modified: 11
- Active contributors: 2 (alice, bob)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 101 lines · 77 tokens per session scan A 77e3aceef9d7
ext-changelog is a skill published in the GitHub repository Caspian-Sun/claude-code-workflow (10 stars, last pushed 7d ago), licensed MIT. It adds 77 tokens to every session and 893 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
kn-commit
Use when committing code changes with proper conventional commit format and verification.
squid-review
Push the committed feature branch, create or update its PR, then run Product Architect acceptance and PR-Reviewer on it. Output: a clean PR with no blockers, or ONE rollup task. Trigger after a feature's tasks are implemented and committed.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
campaign-commit
Choose the correct commit command in a camp, also called a campaign. Use when you are about to commit and need to select camp commit, camp p commit, fest commit, or intentional root pointer sync via camp refs-sync.
fest-execution
Execute active festival tasks. Use when finding the next task, marking tasks completed/blocked/reset, committing with festival traceability, advancing workflow steps, and validating sequence progress.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.