self-ship

Review modified files, apply minimal fixes, commit, and push to the upstream branch.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/hayatosc/dotfiles --skill self-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-ship
Source: https://github.com/hayatosc/dotfiles/tree/main/home/dot_agents/skills/self-ship
Command: npx skills add https://github.com/hayatosc/dotfiles --skill self-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps an AI agent complete the full write → review → commit → push cycle by autonomously reviewing recent changes, applying targeted improvements, and safely publishing them to the remote repository.

Core Features & Use Cases

  • Automated self-review: Re-read each modified file in full, identify correctness, security, simplicity, consistency, and completeness issues, and produce a concise internal review summary.
  • Safe application and publishing: Apply minimal, focused fixes, stage only intended files, verify staged changes, commit with a clear message, and push while respecting branch protections and secret-handling rules.
  • Use Case: After an AI-coded change set, invoke self-ship to audit the edits, correct obvious problems, and push a new commit to the upstream branch without bypassing hooks or exposing secrets.

Quick Start

Request the assistant to self-ship the recent changes by reviewing, fixing issues, committing the modified files, and pushing them to the repository.

Frequently Asked Questions about self-ship

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

FAQPage Schema
How do I automate git commit and push for code changes?

Automate git commit and push by using an autonomous review workflow that re-reads modified files, applies targeted fixes, stages specific files, commits with a descriptive message, and pushes to the upstream branch.

Can an AI agent perform a self-review before pushing code to a git repository?

Yes, an AI agent can perform a self-review before pushing code by reading modified files in full, identifying correctness, security, and completeness issues, and applying minimal fixes before staging and committing.

How does automated code review handle protected branches and secrets in git?

Automated code review handles protected branches and secrets by checking for sensitive data, respecting branch protection rules, and halting for user confirmation on destructive actions like force-push.

What is the best way to commit only specific modified files in an automated workflow?

The best way to commit specific modified files in an automated workflow is to use conservative staging behavior that verifies intended changes, checks for secrets, and commits only those files with a clear message.

Does automated git publishing require manual confirmation for destructive actions?

Automated git publishing requires manual confirmation for destructive actions like force-push, ensuring safe publication by halting operations that might bypass hooks or expose secrets.

Why do I need a self-review step before staging and pushing code changes?

You need a self-review step before staging and pushing code changes to audit edits, correct obvious problems in correctness and simplicity, and ensure completeness before safely publishing a new commit.