home / skills / duc01226 / easyplatform / git-cp

git-cp skill

safe

This skill stages all files, creates a meaningful commit, and pushes the current branch to the remote using git-manager.

npx playbooks add skill duc01226/easyplatform --skill git-cp

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

435 B

---
name: git-cp
description: "[Git & Release] Stage, commit and push all code in the current branch"
infer: true
---

Use `git-manager` agent to stage all files, create a meaningful commit based on the changes and push to remote repository.

## IMPORTANT Task Planning Notes

- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

Overview

This skill automates staging, committing, and pushing all code on the current Git branch using the git-manager agent. It generates a meaningful commit message based on detected changes and executes a safe push to the configured remote. The workflow embeds task planning and a final review step to ensure quality and catch any needed fixes.

How this skill works

The agent scans the working tree to detect modified, added, and deleted files, then stages all changes and composes a descriptive commit message summarizing the edits. It creates the commit locally and pushes to the branch's remote upstream, handling basic push errors. The process is split into small, verifiable tasks and ends with a review task to validate the result.

When to use it

You finished a logical set of changes and want a single, meaningful commit pushed to the branch.
Preparing a quick patch or hotfix that must be staged and pushed without manual Git commands.
Automating a local developer workflow to reduce repetitive git stage/commit/push steps.
When you need a commit message that summarizes the actual file changes rather than typing one manually.

Best practices

Break the work into many small actionable todo tasks before staging and committing.
Review the staged changes before final commit to avoid including unintended files.
Keep commits focused; if changes span different concerns, create separate commits.
Use the final review todo to run tests, linters, or a quick code inspection after push.
Ensure the branch has an upstream set to prevent push failures.

Example use cases

Finish a bugfix: stage related files, generate a commit message describing the fix, and push for review.
Consolidate WIP edits into a single commit before opening a pull request.
Quickly push small documentation updates or formatting changes across many files.
Automated developer assistant stages and pushes small maintenance tasks from a local session.

FAQ

What happens if the push fails due to remote changes?

The agent reports the error and stops; you should pull/rebase as needed, resolve conflicts, then repeat the staged commit/push flow.

Will it include untracked files?

Yes — the agent stages all added, modified, and deleted files unless explicitly excluded by .gitignore.

Can I customize the generated commit message?

You can edit the message before finalizing the commit; the agent provides a summary that you can accept or refine.