← Browse

@https-deeplearning-ai/changelog

B

Maintains CHANGELOG.md in the project root using git commit history. Use when the user invokes /changelog, asks to "update the changelog", "generate a changelog", or wants to record what changed before merging a branch. Creates the file from scratch if it doesn't exist (all commits grouped by date); otherwise appends only commits newer than the last recorded date.

skillclaude

Install

agr install @https-deeplearning-ai/changelog --target claude

Writes 1 file into .claude/skills/, pinned to git-5bc7d96e.

  • .claude/skills/changelog/SKILL.md

Document


name: changelog description: Maintains CHANGELOG.md in the project root using git commit history. Use when the user invokes /changelog, asks to "update the changelog", "generate a changelog", or wants to record what changed before merging a branch. Creates the file from scratch if it doesn't exist (all commits grouped by date); otherwise appends only commits newer than the last recorded date.

Changelog Skill

Workflow

  1. Run the script from the project root:
python3 <skill-dir>/scripts/changelog.py

Where <skill-dir> is the directory containing this skill. Claude Code exposes the skill path — use it directly.

  1. The script handles both cases automatically:

    • No CHANGELOG.md: reads full git history, writes the file with all dates
    • CHANGELOG.md exists: finds the newest ## YYYY-MM-DD heading, fetches commits after that date, prepends new sections
  2. Review the output, edit bullet wording if needed, then commit CHANGELOG.md as part of the merge commit.

Format

# Changelog

## 2026-03-31

- Add responsive design to layout and CSS
- Add Vitest test suite for components and routes

## 2026-03-30

- Initial project scaffold
  • One # Changelog title at the top
  • Date headings as ## YYYY-MM-DD, newest first
  • Each commit is one bullet; wording may be cleaned up manually after generation

Notes

  • Run from the project root (same directory as .git/)
  • Commit subjects come directly from git log; clean them up manually if needed
  • The script is idempotent: re-running when nothing is new prints a message and exits without modifying the file

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-5bc7d96ecbdc2026-07-31