dev-commit

Automate commit, push, and pull request workflows via GitHub CLI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mattjefferson/agents --skill dev-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-commit
Source: https://github.com/mattjefferson/agents/tree/main/skills/dev-commit
Command: npx skills add https://github.com/mattjefferson/agents --skill dev-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of committing staged changes, pushing to the remote repository, and opening a pull request when needed, reducing manual steps and minimizing human error.

Core Features & Use Cases

  • Selective staging: Stage only the files you intend to commit, avoiding accidental inclusions.
  • Conventional commits: Enforce structured commit messages for consistency.
  • Push and PR management: Detect when a PR is needed, create it via gh, and verify upstream tracking.
  • Safety and hygiene: Guardrails for deletions and index.lock handling, and skip PRs on the default branch when appropriate.

Quick Start

Tell me to run the dev-commit workflow on the current repository for specific files to commit and open a PR if needed.

Frequently Asked Questions about dev-commit

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

FAQPage Schema
How do I automate git commit, push, and pull request creation in one workflow?

Automating git commit, push, and pull request creation requires a workflow that stages explicit file paths, generates conventional commit messages, and uses the GitHub CLI to open PRs on non-default branches.

What are conventional commit messages and how do I enforce them in my git workflow?

Conventional commit messages follow a structured format for consistency. You can enforce them in your git workflow by using an automated commit-push-PR process that generates these standardized messages during staging.

How do I safely stage specific files and avoid accidental inclusions before pushing to a remote repository?

To safely stage specific files and avoid accidental inclusions before pushing to a remote repository, use a selective staging process that requires explicit file paths rather than staging all modified files automatically.

Do I need the GitHub CLI installed to automatically create pull requests from my local branch?

Yes, you need the GitHub CLI installed to automatically create pull requests from your local branch. The automation uses the gh command-line tool to detect when a PR is needed and open it on non-default branches.

Why does my automated git workflow fail when the index.lock file is present?

An automated git workflow fails when the index.lock file is present because it indicates a stale git process. A robust commit-push-PR workflow includes index.lock handling guardrails to safely bypass this conflict.

When should I skip creating a pull request during an automated commit and push workflow?

You should skip creating a pull request during an automated commit and push workflow when committing directly to the default branch. The workflow verifies upstream tracking and skips PRs on default branches when appropriate.