AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

github-release

Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read github--github-release at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 3

references/commit-classification.md

Commit Classification Heuristics

Role in the workflow: Commit messages are a secondary signal. The code diff is always read first and treated as ground truth. Use these heuristics to add intent and context on top of what the diff already shows — not to replace it. When a commit message contradicts the diff, trust the diff.

When reading git log output, map each commit to one of the categories below. Repos that follow Conventional Commits (https://www.conventionalcommits.org/) will have explicit prefixes — use them directly. For freeform commit messages, use the heuristics.


Conventional Commit prefixes → category

| Prefix | Category | |---|---| | feat: / feat(scope): | feat | | fix: / fix(scope): | fix | | perf: | perf | | refactor: | refactor | | docs: | docs | | chore: | chore | | test: / tests: | test | | ci: | chore | | build: | chore | | style: | chore | | revert: | depends on what was reverted | | BREAKING CHANGE in footer or ! after type (e.g. feat!:) | breaking |


Freeform commit message heuristics

Breaking:

  • Contains words: breaking, incompatible, remove, rename, drop support
  • Phrase patterns: no longer, was removed, has been deleted, breaking change

Feat (new feature):

  • Starts with: add, implement, introduce, support, new
  • Contains: now supports, ability to, can now

Fix:

  • Starts with: fix, patch, resolve, correct, handle
  • Contains: bug, regression, crash, error, wrong, incorrect, broken

Perf:

  • Contains: speed up, faster, reduce memory, optimize, performance

Refactor:

  • Contains: refactor, clean up, reorganize, restructure, simplify, extract

Docs:

  • Contains: docs, readme, comment, example, typo

Chore:

  • Contains: bump, upgrade dependencies, update deps, version bump, ci, lint

Test:

  • Contains: test, spec, coverage, fixture

Classifying merge commits

Merge commits (e.g., Merge pull request #42) are usually noise. Look at the PR title or the commits inside the merge. If the PR title follows Conventional Commits, use that.


When you can't tell

Default to PATCH if the commit looks like maintenance. Escalate to MINOR if there's any mention of new functionality. Escalate to MAJOR only with explicit evidence of a breaking change — don't guess at breaking.


Mapping categories to Keep a Changelog sections

| Category | Changelog section | |---|---| | breaking + new behavior | Changed | | breaking + removal | Removed | | feat | Added | | fix, perf | Fixed | | security | Security | | refactor, docs, chore, test | Omit (unless user-visible) |

User-visible refactor example: Extracting a previously internal helper into a new public export → treat as Added, not Refactor.