skills.rest
bdsqqq
bdsqqqCOMMUNITY
Explore all skills by this author →
Website𝕏@bedesquiGitHub

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

59|5|Updated Jun 21, 2025
Search Tags:#git#git commit#git push#conventional-commits#stage#git add
One-click install
npx skills add https://github.com/bdsqqq/dots --skill git-ship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-ship
Source: https://github.com/bdsqqq/dots/tree/main/user/amp/skills/git-ship
Command: npx skills add https://github.com/bdsqqq/dots --skill git-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you stage only your changes, enforce conventional commit messages, and push safely, avoiding accidental commits from others or auto-inclusion of unrelated changes.

Core Features & Use Cases

  • Explicit staging: Stage only files you modified to prevent unintended changes from being committed.
  • Conventional commits: Use a standardized format like feat(scope): description for readability and tooling.
  • Safe push guidance: Avoid force pushes; learn strategies to recover when things go off track.

Quick Start

Stage only your changes:

  • git status
  • git add path/to/file
  • git diff --staged
  • git commit -m "feat(scope): description"
  • git push

Frequently Asked Questions about git-ship

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

FAQPage Schema
How do I stage only my changes before committing in a shared repository?▼

Stage only your changes by explicitly adding files with `git add path/to/file`, then verify with `git status` and `git diff --staged` before committing. This prevents accidental inclusion of others' modifications or unrelated changes in your commit.

What is the conventional commits format and why should I use it?▼

Conventional commits follow the format `type(scope): description` (e.g., `feat(auth): add login validation`). This standardized format improves readability, enables automated tooling, and makes commit history scannable across collaborative teams.

How do I push safely without force pushing in collaborative environments?▼

Push normally with `git push` without force flags. If your history diverges, pull with `git pull --rebase` to realign before pushing. Avoiding force pushes protects shared branches from overwriting others' work.

Can I use this workflow when multiple people are committing to the same branch?▼

Yes. This Skill is designed for collaborative environments where multiple agents contribute. Explicit staging and conventional commits ensure only your changes are tracked and the history remains clean and trackable.

What should I do if my local branch diverges from the remote?▼

Use `git pull --rebase` to reapply your commits on top of the remote changes, avoiding merge commits. Then push normally. This keeps history linear and prevents conflicts in shared repositories.

Related Skills

Explore More Software Engineering Skills→
slamb2kslamb2k
5

start-right

Automate end-to-end repository initialization and scaffolding for new projects.

Community
Advanced
irudikirudik
6

commit

Automate Git commit, pull request, and merge cycles via GitHub CLI.

Community
Intermediate
hairihouhairihou

git-conventions

Enforce Conventional Commits syntax for Git commit messages and branch naming.

Community
Basic
paywherebpaywhereb

squash

Squash all branch commits into one via interactive git rebase.

Official
Intermediate