commit

Creates focused Git commits and GitHub pull requests following OpenSpec SDD workflow standards.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill commit-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/ai-specs/skills/commit
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill commit-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork from creating clean, reviewable commits and pull requests by enforcing repository standards, Conventional Commit messages, and spec-driven development readiness checks before anything is pushed. ## Core Features & Use Cases - Scoped Commit Creation: Inspects the working tree, stages only relevant changes, excludes secrets and build artifacts, and writes Conventional Commit messages in English. - GitHub Pull Request Management: Pushes branches and creates or updates PRs via GitHub CLI, always targeting the develop branch with a structured PR body covering summary, OpenSpec change, and verification status. - SDD Readiness Validation: Checks OpenSpec change artifacts (proposal, tasks, specs, reports) to confirm implementation, testing, and review are complete before committing. - Use Case: After finishing a product-catalog feature, ask the assistant to commit the work; it stages only catalog-related files, verifies tests and adversarial review passed, commits with a proper message, pushes the branch, and opens a PR against develop. ## Quick Start Ask the assistant to commit the current changes for the product-catalog change and open a pull request against develop.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create a commit and pull request with GitHub CLI?▼

Stage the relevant files with git add, commit using a Conventional Commit message, push the branch with git push -u origin, then run gh pr create --base develop. The skill automates this sequence after inspecting the working tree.

How do I commit only changes related to one feature?▼

Pass a feature label, branch name, or OpenSpec change name as an argument so only matching files are staged. Files containing mixed changes are handled with git add -p patch staging to select relevant hunks.

Can I get a commit message without running any Git commands?▼

Yes, request a dry run by saying 'no git', 'only message', or 'do not commit'. The skill then outputs the files that would be staged, the proposed commit message, and the PR title and body without modifying anything.

Which branch should a feature pull request target?▼

Feature pull requests must always target the develop branch, never master or main. The master branch only receives changes through an explicit develop-to-master release PR when the user requests it.

What happens if verification or review is incomplete before committing?▼

The skill checks OpenSpec artifacts for completed tasks, test evidence, and adversarial review results. If blockers or missing evidence are found, it reports the gaps and asks before proceeding, unless a work-in-progress commit is explicitly requested.