commit

Stage and commit code changes using Conventional Commits format.

294|54|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/owainlewis/blueprint --skill commit-owainlewis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/owainlewis/blueprint/tree/main/skills/commit
Command: npx skills add https://github.com/owainlewis/blueprint --skill commit-owainlewis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of staging and committing code changes, ensuring consistency and adherence to best practices with Conventional Commits.

Core Features & Use Cases

  • Automated Staging: Intelligently stages relevant files, avoiding accidental inclusion of secrets or unnecessary files.
  • Conventional Commits: Generates commit messages following the type(scope): description format, improving commit history readability and automation.
  • Use Case: After completing a new feature, use this Skill to stage only the modified feature files and create a commit with a feat: type, ready for review.

Quick Start

Use the commit skill to stage all changes and create a commit with the message "feat: implement user authentication".

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate staging and committing code with Conventional Commits?

To automate staging and committing code with Conventional Commits, use this Skill to intelligently stage modified files and generate commit messages formatted as type(scope): description, ensuring readable version control history.

What is the Conventional Commits format for a git commit message?

The Conventional Commits format structures git commit messages as type(scope): description. This Skill automatically generates messages following this specification to improve commit history readability and enable automation.

Can I provide a custom override for an automated conventional commit message?

Yes, you can provide custom overrides for conventional commit messages. This Skill supports automatic message generation based on project conventions but allows user-provided overrides for specific staging and committing needs.

How do I stage only modified feature files without including secrets?

To stage only modified feature files without including secrets, this Skill intelligently stages relevant code changes during the git commit process, avoiding accidental inclusion of unnecessary files to maintain version control safety.