OpenParable
Skip to content
← Back to skills

Commit Push

DevOps & Security
commit-push

Commit Push is an Agent Skill for devops & security published in the anyproto/anytype-ts repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Commit staged/unstaged changes and push to the remote branch in one step

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/anyproto/anytype-ts/blob/HEAD/.claude/skills/commit-push/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/commit-push, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Commit & Push Skill

Commit all current changes and push to the remote in a single workflow.

Process

  1. Check state — Run git status (no -uall), git diff (staged + unstaged), and git log --oneline -5 in parallel
  2. Abort if clean — If there are no changes, inform the user and stop
  3. Stage files — Add changed files by name (never use git add -A or git add .). Skip files that look like secrets (.env, credentials, tokens)
  4. Draft commit message — Follow the repo's JS-XXXX: short description convention. Summarize the "why", not the "what"
  5. Commit — Use a HEREDOC for the message. Always append the co-author trailer: 
    Co-Authored-By: Claude Opus 4.6 <[email protected]>
  6. Push — Push to the current remote-tracking branch (typically origin/develop). Use git push (never force-push)
  7. Confirm — Show the resulting commit hash and remote status

Rules

  • Never amend existing commits
  • Never force-push
  • Never skip hooks (--no-verify)
  • Never commit files that contain secrets
  • Always create a NEW commit, even after a hook failure
  • Push target is always the current branch's upstream (usually develop)