commit

Run quality checks, create conventional commits, and open pull requests via GitHub CLI.

396|51|Updated Mar 14, 2025
One-click install
npx skills add https://github.com/decocms/mesh --skill commit-decocms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/decocms/mesh/tree/main/.cursor/skills/commit
Command: npx skills add https://github.com/decocms/mesh --skill commit-decocms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare code for review by running quality checks, creating conventional commits, and opening pull requests. Use when the user wants to commit changes, create a PR, prepare for code review, or asks to commit their work.

Core Features & Use Cases

  • Quality Assurance Checks: Run bun run fmt, bun run lint, bun run check:ci, bun run knip, bun test. If any checks fail, address issues before proceeding.
  • Create Commits: Split the file changes into logical conventional commits following the Conventional Commit format: type(scope): message. Push all commits to the remote branch.
  • Create or Update Pull Request: Use the gh CLI tool to create or update the PR. The PR description MUST follow the structure defined in .github/pull_request_template.md. Read the template and follow its structure exactly. Analyze the git diff and commits to generate content for each section. For "How to Test", provide specific, actionable steps based on the actual changes. Include the PR URL in the final report.
  • Guardrails: Ensure commit messages and PR metadata meet project standards and safety checks.

Quick Start

Ask me to prepare commits for review and I will run the QA checks, generate conventional commits, and open or update the pull request.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate pull request creation with conventional commits?

To automate pull request creation, you can run quality checks, generate conventional commit messages, and use GitHub CLI to open a PR with a description formatted from your project's pull request template.

What's the best way to prepare code changes for review before pushing?

The best way to prepare code changes for review is to run local quality checks like formatting and linting, address any failures, and split file changes into logical conventional commits before pushing to your remote branch.

How does a conventional commit generator handle code review validation?

A conventional commit generator handles code review validation by executing automated test runs, linting, and formatting checks, ensuring that any code quality issues are addressed before the changes are committed and surfaced for review.

Does the GitHub CLI support automated pull request descriptions from templates?

Yes, the GitHub CLI supports automated pull request descriptions by reading the .github/pull_request_template.md file, analyzing the git diff and commits, and generating actionable content for each section of the template.

Can I split file changes into multiple logical commits automatically?

Yes, you can split file changes into multiple logical commits automatically by grouping related modifications and generating conventional commit messages that follow the type(scope): message format for each logical change.

Why do my automated QA checks fail before I can create a pull request?

Automated QA checks fail before creating a pull request when formatting, linting, CI checks, or tests detect code quality issues, requiring you to address these failures before proceeding with the commit process.