Skills Guide

Code validation and commit

VerifiedSafe

Validates and commits code to the current or new feature branch. Runs checks (lint, build, test) before commit if requested.

Sby Skills Guide Bot
DevelopmentIntermediate
306/2/2026
Claude CodeCursorWindsurf
#git#version-control#conventional-commits#commit-workflow

Recommended for

Backend developerClaude CodeCode reviewCursorFrontend developerFullstack developer

Our review

Automates code commits by optionally running checks, creating feature branches, and drafting conventional commit messages.

Strengths

  • Enforces conventional commit format for better traceability
  • Integrates pre-commit checks (lint, build, tests) to catch issues early
  • Automatically creates feature branches from main
  • Filters out sensitive files to prevent accidental leaks

Limitations

  • Depends on the user's existing Git setup and tool availability
  • Does not handle complex partial commits or conflict resolution
  • Assumes a linear feature branch workflow
When to use it

Use this skill when you want to commit changes with a consistent, verified workflow and standardized commit messages.

When not to use it

Avoid using it when you need to commit partial changes or when using a non-standard commit format.

Security analysis

Safe
Quality score90/100

The skill describes a standard git commit workflow using bash commands for git operations; no destructive, exfiltrating, or obfuscated actions. It does not instruct to run arbitrary network commands or disable safety measures.

No concerns found

Examples

Commit with default checks
Commit my changes.
Force commit without checks
Force commit the current changes, skipping verification.
Commit and create a new branch
Commit the changes to a new feature branch.

name: commit description: Optionally checks, then commits code to the current or a new feature branch.

When asked to commit code, follow these steps:

Arguments

  • check (default): Run checks first to lint, build, and test the code. Stop if any checks fail.
  • force: Skip the check step and commit directly.

Steps

  1. Run these bash commands in parallel to understand the current state:

    • git status to see all untracked files
    • git diff HEAD to see both staged and unstaged changes
    • git log --oneline -10 to see recent commit messages for style consistency

  2. If you are on the main branch, create a new feature branch using git branch and switch to it.

  3. Analyze all changes and draft a commit message:

    • Summarize the nature of the changes (new feature, enhancement, bug fix, refactoring, test, docs, etc.)
    • Use the conventional commit format: type(scope): description
    • Keep the first line under 72 characters
    • Do not commit files that likely contain secrets (.env, credentials.json, etc.)

  4. Stage and commit the changes:

    • Add relevant files using git add
    • Use a plain string for the commit message (do not use HEREDOCs).

  5. Report the results including:

    • The commit hash
    • The commit message
Related skills

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin