commit-push

Commits and pushes only files changed in the current conversation thread.

Updated May 20, 2026
One-click install
npx skills add https://github.com/TeXmeijin/agent-skills --skill commit-push-texmeijin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/TeXmeijin/agent-skills/tree/main/.apm/skills/commit-push
Command: npx skills add https://github.com/TeXmeijin/agent-skills --skill commit-push-texmeijin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with an AI assistant, unrelated changes often accumulate in the working tree. This Skill commits and pushes only the files modified during the current conversation, preventing accidental inclusion of unrelated work and protecting against mistakes on protected branches. ## Core Features & Use Cases - Scoped Commits: Stages and commits only the files changed in this thread, leaving other working-tree changes untouched. - Branch Safety Checks: Verifies the current branch before committing, and requires explicit confirmation before committing directly to main or production branches. - Sequential Execution: Runs commit and push strictly in order so Git hooks like lint-staged can complete before pushing. - PR Creation: After pushing, offers to create a pull request via the gh CLI if none exists for the branch. - Use Case: You finished a feature fix in a long chat session with mixed uncommitted changes. Invoke this Skill to commit only the relevant files, push them, and open a PR against develop. ## Quick Start Ask the assistant to commit and push only the files changed in this thread, then create a PR if one does not exist yet.

Frequently Asked Questions about commit-push

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

FAQPage Schema
How do I commit only specific changed files in git?

Stage only the files you want with git add followed by explicit file paths, then commit. This Skill automates that by tracking which files were modified in the current conversation and staging only those.

How to create a GitHub pull request from the command line?

Use the GitHub CLI with gh pr create, specifying the base branch, title, and body. This Skill runs gh pr create --base develop with a commitzen-style title after pushing, but only if no PR exists yet for the branch.

Can I commit directly to the main or production branch?

This Skill blocks direct commits to main or production unless you explicitly confirm you want to commit there. It first asks whether to create a new branch, preventing accidental commits to protected branches.

Why should commit and push not run in parallel?

Git hooks like lint-staged run during commit and can fail or modify files. Pushing before the commit succeeds risks pushing nothing or an inconsistent state, so this Skill enforces strictly sequential execution.

What happens if I run this on the develop branch?

If you pass develop as an argument, the Skill skips the protected-branch confirmation and commits and pushes directly. Without that explicit argument, it still verifies the branch before proceeding.