git-commit-review-push

Name: git-commit-review-push
Availability: InStock
Author: generic-automation-and-it

Commits changes as Conventional Commits chunks, appends the /ai-review trigger, and pushes to remote.

Updated Jul 23, 2026

Search Tags:#git #code review #conventional commits #push #commit message #branch naming #ci automation

Ready to run

npx skills add https://github.com/generic-automation-and-it/smooth-ai-stockanalysis --skill git-commit-review-push-generic-automation-and-it

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit-review-push
Source: https://github.com/generic-automation-and-it/smooth-ai-stockanalysis/tree/main/.agents/skills/git-commit-review-push
Command: npx skills add https://github.com/generic-automation-and-it/smooth-ai-stockanalysis --skill git-commit-review-push-generic-automation-and-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually crafting Conventional Commit messages, remembering to embed the /ai-review full-review trigger in the final commit, and keeping branch names consistent with the issue tracker is error-prone. This Skill automates the entire commit-and-push workflow so every pushed PR reliably triggers a full AI code review. ## Core Features & Use Cases - Chunked Conventional Commits: Analyzes the working-tree diff, groups changes into logical units, and commits each with a properly formatted Conventional Commits message. - Mandatory /ai-review Trigger: Appends the /ai-review trigger as the final body line of the last commit only, verifies it with an anchored regex check, and amends with the full %B message (preserving trailers) if missing — while safely skipping merge commits. - Branch Rename & Push: Optionally renames the branch to <type>/<issue>-short-description via --issue and pushes with upstream tracking. - Use Case: After finishing a feature, run the skill with --issue 42 to get clean chunked commits, a conforming branch name like feat/42-add-auth, and a push that forces the CI gate to run a full AI review. ## Quick Start Ask the AI to commit my current changes with conventional commits, add the /ai-review trigger, rename the branch for issue 42, and push.

Frequently Asked Questions about git-commit-review-push

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

FAQPage Schema

How do I commit changes with Conventional Commits format and push?▼

Run the skill with an optional commit message; it analyzes the diff, groups changes into logical chunks, and commits each with a Conventional Commits message like feat(auth): add login. It then pushes to the remote, setting upstream if the branch was renamed.

How do I trigger a full AI code review on a pull request?▼

Append /ai-review as the final non-empty line of the last commit's message body. The pipeline-code-review-report.yml gate greps PR commit messages for this trigger and forces a full review; earlier chunk commits must not carry it.

Why does the /ai-review trigger check fail on merge commits?▼

A merge commit's %b body returns the merged-branches list, not a usable message body, so the check would spuriously fail. The skill detects merges via multiple parents or a Merge subject prefix and skips the check entirely.

How do I rename a git branch to match an issue number before pushing?▼

Pass --issue <number> and the skill renames the branch to <type>/<issue>-short-description, deriving the type from the Conventional Commit just made and the description from the diff. It skips the rename if the branch already conforms.

Does this skill create or update pull requests?▼

No. It only commits and pushes changes to the remote repository. Pull request creation or updates must be handled separately; the skill's scope ends after git push.