skills.rest
fredmilhome
fredmilhomeCOMMUNITY
Explore all skills by this author →
GitHub

commit

Automate the commit-PR-merge workflow with pre-commit quality checks.

Updated Jun 27, 2026
Search Tags:#git#commit#GitHub#merge#PR
One-click install
npx skills add https://github.com/fredmilhome/laffer_tobacco --skill commit-fredmilhome
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/fredmilhome/laffer_tobacco/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/fredmilhome/laffer_tobacco --skill commit-fredmilhome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the commit, pull request (PR), and merge process, ensuring explicit intent and high-quality commits.

Core Features & Use Cases

  • Explicit Commit Intent: Ensures users only commit when they explicitly request it, reducing accidental commits.
  • Quality Gates: Implements quality checks before commits to maintain code quality.
  • Automated Workflow: Handles the entire commit-PR-merge cycle with minimal manual intervention.

Quick Start

To commit changes and create a pull request, simply say "commit" followed by your commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate the git commit, PR, and merge process?▼

Automate the commit-PR-merge workflow by explicitly stating your intent to commit. This triggers pre-commit quality checks and handles the entire pull request cycle with minimal manual intervention.

Do I need GitHub CLI to automate pull request creation?▼

Yes, you need both git and GitHub CLI installed to automate pull request creation. These dependencies are required for executing the repository operations and merge process.

Can I skip pre-commit hooks when automating a commit?▼

No, this workflow prevents skipping hooks or executing force-pushes. It implements quality gates before commits to maintain code quality and ensure safe repository operations.

How does explicit intent prevent accidental git commits?▼

Explicit intent requires users to specifically request a commit action, reducing accidental commits. This ensures changes are only committed when deliberately triggered during the workflow.

What's the best way to create a pull request after local changes?▼

Use an automated workflow that handles the entire commit-PR-merge cycle. Simply provide your commit message explicitly to trigger the process and create the pull request automatically.

Are there limitations when using automated commit and merge workflows?▼

Yes, the workflow requires explicit user intent for commits and enforces pre-commit checks. It prevents force-pushes and hook skipping, which may limit rapid workarounds during development.

Related Skills

Explore More Software Engineering Skills→
tile-aitile-ai
346

tilelang-github-operations

Install GitHub CLI and create pull requests via authenticated workflows.

Official
Advanced
jimmymalhanjimmymalhan
1

rebase-manager

Rebase dependent pull request branches onto main after a base PR merges.

Community
Intermediate
baphledbaphled
1

check-compliance

Run linting, formatting, security scans, and tests before committing code.

Community
Intermediate
dzineerdzineer

update-2-git-with-diff

Generate a Git diff, create a pull request, and merge into the main branch.

Community
Intermediate