skills.rest
rpamis
rpamisOFFICIAL
Explore all skills by this author →
GitHub

comet-safe-delivery

Commits, pushes, and delivers scoped Git changes while protecting unrelated worktree modifications.

2.9k|284|Updated May 14, 2026
Search Tags:#Git#worktree#push#code delivery#submodule#Version Control#Commit
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-safe-delivery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-safe-delivery
Source: https://github.com/rpamis/comet/tree/main/assets/skills-maintainer/comet-safe-delivery
Command: npx skills add https://github.com/rpamis/comet --skill comet-safe-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivering code changes in a messy working tree risks accidentally committing unrelated dirty files, switching branches silently, or breaking submodule states. This Skill enforces a disciplined, authorization-first Git delivery workflow so only explicitly scoped changes are committed and pushed.

Core Features & Use Cases

  • Scoped Staging and Verification: Stages only confirmed target paths, then validates with git diff --cached --name-status, --stat, and --check before committing.
  • Worktree and Submodule Safety: Records branch, upstream, and worktree state first; commits submodules before updating the parent repo gitlink.
  • Controlled Delivery: Commits with typed prefixes (e.g., fix:, docs:), pushes only user-specified branches and remotes, and verifies commit SHA, upstream, and remote branch state afterward.
  • Use Case: A maintainer has a mixed working tree with unrelated edits and asks to deliver only the prepared fix; the Skill stages just those paths, runs pre-commit hooks, commits, pushes to the specified remote, and reports commit, push, and CI status separately.

Quick Start

Use the comet-safe-delivery skill to commit and push only my confirmed changes to the current branch.

Frequently Asked Questions about comet-safe-delivery

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

FAQPage Schema
How do I commit only specific files in a dirty Git working tree?▼

Stage only the explicitly confirmed target paths instead of using broad staging commands like git add -A. Then verify the staged set with git diff --cached --name-status and --stat before committing.

How to safely push changes when working with Git worktrees?▼

First record the current branch, upstream, git status, and git worktree list output to understand all linked worktrees. Push only the user-specified branch and remote, and never silently switch branches or change the delivery target.

Does this skill handle Git submodules during delivery?▼

Yes. It checks each submodule's own branch and status first, and when delivery is authorized it commits the submodule before updating the parent repository's gitlink.

What happens if a pre-commit hook modifies staged files?▼

The skill lets repository pre-commit hooks run normally, then re-checks the staged file names and diff if the hook modified staged content. This ensures the final commit matches the confirmed scope.

Will this skill create pull requests or delete branches automatically?▼

No. Unless explicitly requested, it does not create PRs, merge remote branches, delete branches, remove worktrees, or rewrite history. Deletion of worktrees or branches requires confirming relationships, exact targets, and recoverability.

Related Skills

Explore More Software Engineering Skills→
continuedevcontinuedev
35.4k

cn-check

Run the Continue CLI locally to check working tree changes with Node.js 18+.

Official
Intermediate
dobrinz123dobrinz123

gsd-ship

Push branches, create pull requests, and monitor merge status.

Community
Intermediate
rickyanandarickyananda
1

requesting-code-review

Review staged git diffs for security, logic, and regression issues.

Community
Advanced
Awish021Awish021
10

prepare-commit-changes

Stage specific code hunks for Git commits using hunk ID formats.

Community
Intermediate