sf-ship

Stage, commit, and push Git changes with task tracking integration.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/diane-defores/shipflow --skill sf-ship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sf-ship
Source: https://github.com/diane-defores/shipflow/tree/main/skills/sf-ship
Command: npx skills add https://github.com/diane-defores/shipflow --skill sf-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the final steps of code delivery by managing staging, committing, and pushing changes efficiently, supporting fast iteration and professional release practices.

Core Features & Use Cases

  • Simplifies Git Operations: Handles staging and committing only relevant files for quick pushes.
  • Supports Workflow Closure: Updates task trackers and changelogs when closing a task fully.
  • Use Case: A developer wants to rapidly push code updates during active development without manual staging or bookkeeping.

Quick Start

Use the sf-ship skill to stage, commit, and push your current changes with the message "my latest update."

Frequently Asked Questions about sf-ship

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

FAQPage Schema
How do I automate git commits and pushes for rapid development?▼

You can automate git commits and pushes by using a skill that stages relevant files, commits with a message, and pushes changes directly. This removes manual staging steps, allowing developers to quickly iterate and close code updates during active development workflows.

What is the best way to close task tracking workflows after pushing code?▼

The best way to close task tracking workflows after pushing code is to update task trackers and changelogs as part of the final delivery steps. This integrates task management closure directly into the git push procedure for professional release practices.

Do I need Git installed to automate staging and pushing code changes?▼

Yes, Git is required to automate staging and pushing code changes. The underlying version control operations rely on Git to execute the staging, committing, and pushing procedures within your development environment.

Can I commit only specific files when automating my git push workflow?▼

Yes, the automation supports committing only specific files by handling staging and committing relevant files selectively. This ensures unrelated changes remain untracked during quick iteration pushes in your git workflow.

When should I avoid automating git staging and task closure?▼

Automating git staging and task closure should be avoided for complex merge conflicts or multi-branch release strategies requiring manual review. It is designed for frequent code updates and quick iteration rather than intricate manual bookkeeping.