Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
Automatically generate user-facing release notes from git commits, pull requests, changelogs, and code changes.
$ npx skills add ArabelaTso/Skills-4-SE --skill release-notes-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ArabelaTso/Skills-4-SE release-notes-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release-notes-writer .claude/skills/release-notes-writer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-notes-writer" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/release-notes-writer into .claude/skills/release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/release-notes-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ArabelaTso/Skills-4-SE --skill release-notes-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ArabelaTso/Skills-4-SE release-notes-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/release-notes-writer .agents/skills/release-notes-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-notes-writer" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/release-notes-writer into .agents/skills/release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ArabelaTso/Skills-4-SE --skill release-notes-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ArabelaTso/Skills-4-SE release-notes-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/release-notes-writer .cursor/skills/release-notes-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-notes-writer" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/release-notes-writer into .cursor/skills/release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ArabelaTso/Skills-4-SE.git --path skills/release-notes-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ArabelaTso/Skills-4-SE --skill release-notes-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ArabelaTso/Skills-4-SE release-notes-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/release-notes-writer .gemini/skills/release-notes-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-notes-writer" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/release-notes-writer into .gemini/skills/release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ArabelaTso/Skills-4-SE release-notes-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ArabelaTso/Skills-4-SE --skill release-notes-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/release-notes-writer .github/skills/release-notes-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-notes-writer" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/release-notes-writer into .github/skills/release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ArabelaTso/Skills-4-SE --skill release-notes-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ArabelaTso/Skills-4-SE release-notes-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/release-notes-writer .opencode/skills/release-notes-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-notes-writer" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/release-notes-writer into .opencode/skills/release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
release-notes-writerAutomatically generate user-facing release notes from git commits, pull requests, changelogs, and code changes.
Release Notes Writer is an agent skill from ArabelaTso/Skills-4-SE. Automatically generate user-facing release notes from git commits, pull requests, changelogs, and code changes. Use when preparing software releases, creating version announcements, documenting what changed between versions, or communicating updates to users. Analyzes commit messages, PR descriptions, and code diffs to produce categorized markdown release notes organized by New Features, Improvements, Bug Fixes, and Breaking Changes. Focuses on user-visible changes while filtering out internal/technical details…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes, Commit messages and Pull requests. The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4f38503. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitghFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Release Notes Writer loads about 2.3k tokens when it runs. Until then it costs about 168 tokens; SKILL.md has 451 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 451 words, ~2,294 tokens.
.claude/skills/release-notes-writer/SKILL.md (or your agent's skills folder).Generate polished, user-facing release notes from git history, pull requests, and code changes, automatically categorizing and summarizing changes in a clear, accessible format.
Collect the scope and sources for the release notes:
Define the release scope:
Quick commands to get started:
# Get commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline
# Get commits between two tags
git log v2.0.0..v2.1.0 --oneline
# Get commits since specific date
git log --since="2024-01-01" --oneline
# List all tags
git tag -l
# Get merged PRs (if using GitHub)
gh pr list --state merged --limit 50Gather details from available sources:
# Get commit messages with details
git log v2.0.0..v2.1.0 --pretty=format:"%h - %s (%an)" --no-merges
# Get commits by author
git log v2.0.0..v2.1.0 --author="AuthorName" --oneline
# Get commit messages with full body
git log v2.0.0..v2.1.0 --format="%h %s%n%b%n"Parse commit message conventions:
feat: or feature: → New Featurefix: or bugfix: → Bug Fixperf: or performance: → Performance Improvementdocs: or doc: → Documentationrefactor: → Code Quality/Refactoringtest: → Testingchore: → Internal/MaintenanceBREAKING: or !: → Breaking ChangeIf using GitHub CLI:
# Get merged PRs
gh pr list --state merged --limit 100 --json number,title,body,labels,mergedAt
# Get PR details
gh pr view <PR-NUMBER>Extract from PR:
Check for existing changelog entries:
# Look for changelog files
find . -name "CHANGELOG.md" -o -name "HISTORY.md" -o -name "RELEASES.md"
# Check for unreleased section
grep -A 20 "Unreleased" CHANGELOG.mdInfer changes from code when commits lack detail:
# See what files changed
git diff --stat v2.0.0..v2.1.0
# See what functions/classes were added
git diff v2.0.0..v2.1.0 --unified=0 | grep "^+def\|^+class"
# See API changes
git diff v2.0.0..v2.1.0 -- "*.py" | grep -E "^[+-]def |^[+-]class "Organize changes into standard categories:
User-visible new capabilities:
Examples:
Corrections to existing functionality:
Enhancements to existing features:
Changes requiring user action:
Include:
Exclude or minimize:
Transform technical to user-friendly:
❌ "Refactored AuthService to use dependency injection"
✅ "Improved authentication reliability"
❌ "Updated webpack config for tree shaking"
✅ "Reduced bundle size by 20%"
❌ "Fixed race condition in concurrent processing"
✅ "Improved stability when processing multiple items simultaneously"Create formatted markdown output:
# Release Notes - Version X.Y.Z
**Release Date:** YYYY-MM-DD
## Summary
[1-3 sentence overview of the release]
---
## ✨ New Features
- **[Feature Title]**: [User-friendly description]
- **[Feature Title]**: [Description with benefit]
## 🚀 Improvements
- **[Improvement Title]**: [How this makes things better]
- **[Improvement Title]**: [Description]
## 🐛 Bug Fixes
- Fixed [issue description]
- Resolved [problem users were experiencing]
## ⚠️ Breaking Changes
- **[Breaking Change Title]**: [What changed and what users need to do]
- **Migration:** [Step-by-step guidance]
- **Before:** `code example`
- **After:** `code example`
---
## 📊 Statistics
- X features added
- Y bugs fixed
- Z improvements made
## 🙏 Contributors
Thank you to all contributors who made this release possible:
- @username1
- @username2Make each change clear and valuable:
Use active, benefit-focused language:
❌ "Added pagination to API"
✅ "You can now request data in pages, making it easier to work with large datasets"
❌ "Implemented OAuth2 authentication"
✅ "Sign in with your Google, GitHub, or Microsoft account"
❌ "Optimized database queries"
✅ "Reports now load 3x faster"Be specific about impact:
❌ "Performance improvements"
✅ "Search results now appear in under 100ms, down from 2 seconds"
❌ "Better error handling"
✅ "Error messages now include specific suggestions for fixing the issue"Include code examples for API changes:
### Breaking Change: Authentication Method Updated
**Before:**
```python
client = APIClient(session_token="abc123")After:
client = APIClient(api_key="sk-abc123")Migration: Update your initialization code to use the new api_key parameter.
### 7. Review and Polish
Before finalizing:
**Check completeness:**
- ✅ All significant changes included?
- ✅ Breaking changes clearly marked?
- ✅ User action items specified?
- ✅ Version number correct?
**Check clarity:**
- ✅ Descriptions are user-friendly, not technical?
- ✅ Benefits are clear?
- ✅ No internal jargon?
- ✅ Examples provided where helpful?
**Check organization:**
- ✅ Changes grouped logically?
- ✅ Most important changes listed first?
- ✅ Breaking changes prominently displayed?
## Example Output
```markdown
# Release Notes - Version 2.3.0
**Release Date:** February 15, 2026
## Summary
Version 2.3.0 brings enhanced search capabilities, performance improvements, and several bug fixes.
---
## ✨ New Features
- **Advanced Search Filters**: Filter search results by date, category, and status for more precise results
- **Keyboard Shortcuts**: Navigate the app faster with new keyboard shortcuts (press `?` to see all)
- **Export to Excel**: Export your data to Excel format in addition to CSV
## 🚀 Improvements
- **Faster Search**: Search results now appear instantly (improved from 2s to <100ms)
- **Better Mobile Experience**: Optimized interface for mobile devices
- **Smarter Autocomplete**: Autocomplete suggestions now learn from your previous searches
## 🐛 Bug Fixes
- Fixed issue where saving large files would occasionally fail
- Resolved problem with date picker not working in Safari
- Corrected timezone display for users in Asia-Pacific regions
---
## 📊 Statistics
- 3 new features
- 4 bugs fixed
- 3 improvements
- 47 commits
- 8 contributors
## 🙏 Contributors
Thank you to: @alice, @bob, @charlie, @diana, @eve, @frank, @grace, @henryFocus on user value:
Be honest about breaking changes:
Use consistent language:
Group related changes:
Credit contributors:
© ArabelaTso, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/release-notes-writer of ArabelaTso/Skills-4-SE.
Open the folder on GitHubat commit 4f38503
Release Notes Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Notes Writer this skillArabelaTso/Skills-4-SE | 253 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Git Workflow and Versioningaddyosmani/agent-skills | 103k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Commit And PR Messagessuperplanehq/superplane | 7.7k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Plane Release Notes Generatormakeplane/plane | 61k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| PR Pushicebear0828/codex-proxy | 1.8k | — | ~2.2k | Automated safety check: Notes | Custom licence |
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
superplanehq/superplane
Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
ArabelaTso/Skills-4-SE
Generate prioritized CVE watchlists and actionable security recommendations for repositories.
ArabelaTso/Skills-4-SE
Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).
ArabelaTso/Skills-4-SE
Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.
ArabelaTso/Skills-4-SE
Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.
ArabelaTso/Skills-4-SE
Automatically migrate Spring MVC applications to Spring Boot.
ArabelaTso/Skills-4-SE
Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.
Categories
Automatically generate user-facing release notes from git commits, pull requests, changelogs, and code changes. Release Notes Writer is an agent skill from ArabelaTso/Skills-4-SE. Automatically generate user-facing release notes from git commits, pull requests, changelogs, and code changes.
Release Notes Writer fits situations like: preparing software releases; creating version announcements; documenting what changed between versions; communicating updates to users.
Run `npx skills add ArabelaTso/Skills-4-SE --skill release-notes-writer -a claude-code`. Or copy the skill folder (skills/release-notes-writer in ArabelaTso/Skills-4-SE) into .claude/skills/release-notes-writer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ArabelaTso/Skills-4-SE --skill release-notes-writer -a codex`. Or copy the skill folder (skills/release-notes-writer in ArabelaTso/Skills-4-SE) into .agents/skills/release-notes-writer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ArabelaTso/Skills-4-SE --skill release-notes-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-notes-writer, .gemini/skills/release-notes-writer, .github/skills/release-notes-writer and .opencode/skills/release-notes-writer in your project.
Going by SKILL.md and its folder, Release Notes Writer needs the command-line tools its instructions call (git and gh). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Release Notes Writer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Release Notes Writer: Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Commit And PR Messages (superplanehq/superplane, 7.7k stars) and Plane Release Notes Generator (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 150 skills in this directory. The repository was last updated on August 21, 2026.
Source: ArabelaTso/Skills-4-SE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.