SuperAPI AI Directory

comet-safe-delivery

Deployment & operations

View repository

Updated 10-16 01:27

About this skill

Comet Safe Delivery

First read ../comet-github/references/maintainer-contract.md. Only perform Git delivery actions after the user explicitly authorizes them; this Skill will never publish to npm.

Pre-Delivery Checks

  1. Record the current branch, upstream,git status --short --branch and git worktree list --porcelain。
  2. Check the diff to determine the exact target paths. If it overlaps with unrelated changes, confirm the scope first.
  3. Confirm the target branch and remote; do not silently switch branches or change the delivery target.
  4. When submodules are involved, first confirm the submodule's own branch/status; when authorized to deliver, commit the submodule first, then update the parent repository's gitlink.

Staging and Verification

  • Stage only the exact target paths; do not use broad staging commands in a mixed worktree.
  • Check git diff --cached --name-status、git diff --cached --stat and git diff --cached --check。
  • Let the repository's pre-commit hook run normally. If the hook modifies the staged content, re-check the staged filenames and diff.
  • Use a commit message with a type prefix, e.g. fix: ...、docs: ... or chore: ...。

Delivery

Commit only the confirmed staged scope, and push only to the branch and remote explicitly specified by the user. After completion, verify the local status, commit SHA, upstream relationship, and remote branch SHA. Report the commit, push, and online CI status separately.

Unless otherwise requested, do not create a PR, do not merge remote branches, do not delete branches, do not remove worktrees, and do not rewrite history. Before deleting a worktree or branch, confirm the associations, exact target, and recoverability; do not force-delete broad or unresolved paths.