skills.rest
jacobcy
jacobcyCOMMUNITY
Explore all skills by this author →
GitHub

vibe-commit

Groups commits, applies quality gates, and drafts PRs for flows without merging or closing them.

6|Updated Feb 5, 2026
Search Tags:#automation#git#workflow#commit#pr#code-review#flow-management
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vibe-commit
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/skills/vibe-commit
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates and orchestrates the process of grouping changes, preparing commit sets, and creating pull requests across a flow, without handling merge or closure tasks.

Core Features & Use Cases

  • Commit grouping and metadata orchestration: groups related changes into focused commits aligned with a delivery goal.
  • Pre-commit quality gate: ensures formatting and linting are applied before final commits via a two-step process.
  • PR creation and handoff: automates drafting PRs with base branches, flow state, and an optional agent-driven path, then records handoff state.

Quick Start

Register the current work and prepare the PR draft and handoff for the active flow.

Frequently Asked Questions about vibe-commit

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

FAQPage Schema
How do I automate commit grouping and PR creation across a delivery pipeline?▼

To automate commit grouping and PR creation, you orchestrate the process by grouping related changes into focused commits and drafting pull requests with the correct base branches. This records the handoff state without executing merges.

How does a pre-commit quality gate enforce formatting and linting?▼

A pre-commit quality gate enforces formatting and linting through a two-step process applied before final commits. This ensures code quality standards are met directly within the workflow before orchestrating the commit sets.

Can I use this workflow to manage standardized pull requests for complex flows?▼

Yes, you can use this workflow to manage standardized pull requests for complex flows. It coordinates PR creation, captures flow state, and supports an optional agent-driven path to handle delivery pipelines.

Does this commit orchestration process handle merging or closing pull requests?▼

No, this commit orchestration process does not handle merging or closing pull requests. It strictly focuses on preparing commit sets, drafting PRs, and recording the handoff state for downstream execution.

Why should I group related changes into focused commits before creating a PR?▼

You should group related changes into focused commits to align them with a specific delivery goal. This orchestration step ensures the pull request contains structured, purposeful changes rather than disjointed edits.

Related Skills

Explore More Software Engineering Skills→
hayatoschayatosc
1

self-ship

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

Community
Intermediate
arbazkhan971arbazkhan971
26

finish

Finalize feature branches via merge, pull request, keep, or discard after build, lint, and tests.

Community
Advanced
trevin-jtrevin-j
6

git-basics

Run tests, linters, and static analysis before committing with Conventional Commits.

Community
Intermediate
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate