Skills for Real Engineers. Straight from my .agents directory.
39 skills
skillshare-changelog
Agent skill from
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed since last release", this is the skill to use. Do NOT manually edit CHANGELOG.md without this skill — it ensures proper formatting, user-perspective writing, and website changelog sync. For full release workflows (Release PR review, tests, draft assets, publication, announcements), use /release instead.
How to install skillshare-changelog
install skillshare-changelog
# install the skillshare pack with the skills CLI
npx skills add runkids/skillshare# or add only this skill to Claude Code: copy the folder
.skillshare/skills/skillshare-changelog/
# into
~/.claude/skills/skillshare-changelog/ (all projects)
.claude/skills/skillshare-changelog/ (one project)
1Review or generate a user-facing changelog entry. Prefer the open Release Please PR and its manifest version for an upcoming release. For historical work, $ARGUMENTS specifies the requested tag or commit range.23**Scope**: This skill updates `CHANGELOG.md` and syncs the website changelog (`website/src/pages/changelog.md`). It does NOT generate RELEASE_NOTES, choose a new version, or handle the full release workflow — use `/release` for that.45Before acting, run `python3 scripts/ai-context.py release`. That topic is the source of truth for authorization, changelog content and synchronization rules; this skill retains the entry-generation workflow.67## Workflow89### Step 1: Determine Version Range1011For an upcoming release, work on the Release PR branch and read `.github/release-please-manifest.json`. Verify the latest published tag and use its range to the Release PR head. Keep the proposed version; this skill does not authorize a version change. Tags may exist for unpublished drafts, so do not assume the highest local tag is the latest published release.1213For historical work, use the user-requested tags or range.1415### Step 2: Collect Commits1617```bash18git log <previous-published-tag>..<release-pr-head-or-requested-tag> --oneline --no-merges19```2021Review the generated Release Please entry before writing. Preserve useful manual examples and migration notes. Do not add a second entry for the same version.2223### Step 3: Categorize Changes2425Group commits by conventional commit type:26…
Excerpt shown under the repository's MIT license.
More skills in skillshare
Keep exploring
Similar skill repositories
An agentic skills framework & software development methodology that works.
15 skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
CC1 skill
Public repository for Agent Skills
20 skills
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
CCCU6 skills
An AI skill that provides design intelligence for building professional UI/UX across multiple platforms.
CCCXCUGH6 skills