skills.rest
leolionart
leolionartCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

save-and-release

Commit changes, push to the remote branch, and draft release notes.

1|Updated Mar 7, 2026
Search Tags:#automation#git#workflow#commit#save#push#release-notes
One-click install
npx skills add https://github.com/leolionart/claude-skills --skill save-and-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: save-and-release
Source: https://github.com/leolionart/claude-skills/tree/main/plugins/save-and-release/skills/save-and-release
Command: npx skills add https://github.com/leolionart/claude-skills --skill save-and-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Save work flows that are error-prone: turning changes into messy commits, forgetting to push to the right branch, and skipping release-note preparation.

Core Features & Use Cases

  • Auto-generates clean commit messages that reflect the purpose of changes.
  • Pushes the local branch to the appropriate remote after commit, with safeguards.
  • Drafts release notes or a checklist to prepare for a GitHub release when requested.
  • Supports optional GitHub release publishing when the user explicitly asks.

Quick Start

Run the save-and-release flow to commit clean changes, push to the upstream branch, and draft release notes.

Frequently Asked Questions about save-and-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commit, push, and release note generation in one workflow?▼

Automating your git workflow involves generating clean commit messages, pushing to the correct remote branch with tracking safeguards, and drafting release notes. This process ensures a safe, auditable path from local changes to upstream integration and optional GitHub releases.

Can I automatically generate clean commit messages for my git changes?▼

Yes, clean commit messages can be auto-generated to reflect the specific purpose of your changes. The workflow analyzes your diffs to create purposeful messages before pushing to the remote branch, preventing messy or uninformative commits.

How does the release notes drafting process work after pushing code?▼

Release notes drafting works by preparing a checklist or formatted notes for a GitHub release upon your explicit request. Explicit publish steps and diff reviews ensure controlled releases, meaning publishing only happens when you directly ask for it.

What safeguards are applied when pushing local branches to a remote repository?▼

Safeguards applied during remote pushes include diff reviews and branch tracking checks. These mechanisms enforce a controlled release path, preventing accidental pushes to incorrect upstream branches before local changes are integrated.

Do I need to explicitly request GitHub release publishing after a commit and push?▼

Yes, GitHub release publishing requires an explicit request from the user. The workflow drafts release notes and prepares the release, but only executes the actual GitHub release publishing when you directly ask for it, ensuring controlled releases.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

Git Pull

Pull remote Git changes into a local branch with configurable merge or rebase strategies.

Community
Intermediate
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
cxnaivecxnaive

requesting-code-review

Automate pre-commit code verification with static security analysis and regression checks.

Community
Advanced
giosuetedeschi-specgiosuetedeschi-spec

git-pushing

Automate git staging, committing, and pushing to remote repositories.

Community
Basic