How this skill is triggered — by the user, by Claude, or both
Slash command
/psd-coding-system:changelogclaude-opus-4-6This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You generate structured Keep-a-Changelog entries from git history. You read commits, classify changes, and produce a formatted changelog section ready to paste into CHANGELOG.md.
You generate structured Keep-a-Changelog entries from git history. You read commits, classify changes, and produce a formatted changelog section ready to paste into CHANGELOG.md.
Arguments: $ARGUMENTS
# Find the most recent tag as default starting point
LATEST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
echo "Latest tag: ${LATEST_TAG:-none}"
# Use argument if provided, otherwise use latest tag
SINCE="${ARGUMENTS:-$LATEST_TAG}"
if [ -z "$SINCE" ]; then
echo "No tag found and no argument provided."
echo "Usage: /changelog [since-ref]"
echo " e.g., /changelog v1.25.0"
echo " e.g., /changelog HEAD~10"
exit 1
fi
echo "Generating changelog since: $SINCE"
echo ""
# Get current version from plugin.json
CURRENT_VERSION=$(grep -o '"version": *"[^"]*"' plugins/psd-coding-system/.claude-plugin/plugin.json 2>/dev/null | head -1 | sed 's/.*"version": *"//;s/"//')
echo "Current version: ${CURRENT_VERSION:-unknown}"
echo "=== Commits since $SINCE ==="
git log "$SINCE"..HEAD --format="%h %s%n%b---" --no-merges
echo ""
echo "=== Merge commits ==="
git log "$SINCE"..HEAD --format="%h %s" --merges
echo ""
echo "=== Files changed ==="
git diff --stat "$SINCE"..HEAD
Analyze every commit and classify each change into Keep-a-Changelog categories:
Rules:
Get today's date and produce the changelog entry:
TODAY=$(date +%Y-%m-%d)
echo "Date: $TODAY"
Present the formatted changelog entry:
## [VERSION] - DATE
### Added
- **Feature name** — Description of what was added
### Changed
- **Component** — Description of what changed
### Fixed
- **Bug area** — Description of what was fixed
Only include sections that have content. Don't include empty sections.
Then ask the user:
Ready to insert this into CHANGELOG.md? [y/n]
If yes, I'll add it at the top of the file (after the header).
If confirmed, use the Edit tool to insert the new entry at the top of CHANGELOG.md, right before the first existing ## [ version entry.
npx claudepluginhub psd401/psd-claude-plugins --plugin psd-coding-systemGenerates a formatted CHANGELOG.md from git commit history, grouped by type and ready for release.
Creates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.