skills.rest
allemaar
allemaarCOMMUNITY
Explore all skills by this author →
Website𝕏@allemaarGitHub

github-sync

Clusters session git changes into an approved commit plan and pushes to GitHub.

14|1|Updated Jun 14, 2026
Search Tags:#git#code review#version control#commit#github#push#session sync
One-click install
npx skills add https://github.com/allemaar/open-skills --skill github-sync-allemaar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-sync
Source: https://github.com/allemaar/open-skills/tree/main/skills/github-sync
Command: npx skills add https://github.com/allemaar/open-skills --skill github-sync-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending a working session often leaves a pile of uncommitted changes with no clear structure. This Skill reviews the session's git changes, groups them into logical commits, gets your explicit approval on exact commit messages, and pushes to GitHub safely. ## Core Features & Use Cases - Change Clustering: Analyzes git diff and status output to group changes by intent, app, and blast radius into an ordered commit plan. - Approval-Gated Commits: Shows exact full commit messages for approval and never commits or pushes without an explicit yes. - Safety Guardrails: Stages only approved paths, blocks attribution trailers like Co-Authored-By, verifies committed messages byte-for-byte, and never force-pushes. - Use Case: After a long coding session with mixed changes across features and fixes, run /github-sync to split them into clean commits, exclude stray files like .env or debug artifacts, and push only what you approved. ## Quick Start Ask the agent to sync this session to GitHub by reviewing the current changes and proposing a commit plan for approval.

Frequently Asked Questions about github-sync

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

FAQPage Schema
How do I commit and push session changes to GitHub safely?▼

Run /github-sync or say "sync to github". The skill reviews your git diff and status, proposes an ordered commit plan with exact messages, waits for your explicit approval, then stages only approved paths and pushes.

How to split mixed changes into multiple git commits?▼

The skill clusters changes by intent, app or package, and blast radius, defaulting to separate commits for independent changes. It presents each commit's files, reason, and full message for approval before staging anything.

Does this skill commit without asking for approval first?▼

No. It never commits or pushes without an explicit yes to the exact plan shown, including full commit message blocks. Any drift such as new dirty files or changed messages stops the process for a revised plan.

Can I use github-sync for commit-only without pushing?▼

No. The skill's own description states it should not be used for commit-only workflows or partial staging scenarios. It is designed specifically for the full review, approve, commit, and push flow.

Why does the skill block Co-Authored-By trailers in commits?▼

The skill enforces a no-attribution policy, rejecting Co-Authored-By, Generated-by, and AI attribution trailers before push. A Signed-off-by line is allowed only when repository policy explicitly requires DCO.

Related Skills

Explore More Software Engineering Skills→
toqoztoqoz

commit-work

Selectively stage and commit specific hunks of code changes by patch-based isolation.

Community
Advanced
FaeifFaeif

context-save

Save current working context, including git state and decisions.

Community
Intermediate
carlos-algmscarlos-algms
2

requesting-code-review

Request focused code reviews using git status and diff scopes.

Community
Intermediate
laicluselaicluse
4

commit-all-the-things

Groups all uncommitted git changes into logical commits with descriptive messages.

Official
Intermediate