skills.rest
ProteoWizard
ProteoWizardOFFICIAL
Explore all skills by this author →
WebsiteGitHub

version-control

Enforce team-specific Git commit formats and gate commits, pushes, and pull requests.

17|2|Updated Jan 10, 2026
Search Tags:#git#workflow#pre-commit#version-control#branch-naming#commit-messages
One-click install
npx skills add https://github.com/ProteoWizard/pwiz-ai --skill version-control-proteowizard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version-control
Source: https://github.com/ProteoWizard/pwiz-ai/tree/main/claude/skills/version-control
Command: npx skills add https://github.com/ProteoWizard/pwiz-ai --skill version-control-proteowizard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce team-specific Git commit formats and gate Git operations to prevent unreviewed changes and broken builds.

Core Features & Use Cases

  • Enforces pre-commit gates that require successful build and tests before staging or committing.
  • Validates commit message formats and requires proper co-authoring and TODO references.
  • Guides developers to read version-control and workflow documentation before performing GitHub actions. Use cases include standardizing commits across releases, ensuring PR correctness, and maintaining branch naming discipline.

Quick Start

Run this skill before committing to ensure compliance with team conventions.

Frequently Asked Questions about version-control

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

FAQPage Schema
How do I enforce a specific Git commit message format for my team?▼

This Skill gates Git operations by validating structured commit message formats during local commits and pull requests, requiring TODO references and co-authored-by credits to ensure team-wide process compliance.

What are pre-commit Git hooks and how do they prevent broken builds?▼

Pre-commit Git hooks are gates that require successful builds and tests before staging or committing. This Skill enforces these checks locally to prevent unreviewed changes and broken builds from entering the repository.

How do I standardize branch naming conventions and pull request checks?▼

You can standardize branch naming and PR checks by running this Skill before committing. It enforces branch naming discipline and validates PR correctness to maintain consistent release standards across the development workflow.

Do I need to read version-control documentation before making Git commits?▼

Yes, this Skill guides developers to read version-control and workflow documentation before performing GitHub actions, ensuring proper code quality and process compliance prior to staging or committing changes.

Can I use this to gate Git pushes and pull requests across a specific development team?▼

Yes, this Skill applies gates during local commits, pushes, and pull requests across Skyline and ProteoWizard development to enforce team-specific conventions and prevent unreviewed changes from merging.

Related Skills

Explore More Software Engineering Skills→
jpoutrinjpoutrin
14

git-commits

Enforce Conventional Commits format for Git commit messages.

Community
Basic
quan0715quan0715
31

qjudge-github-workflow-owner

Enforce branch, commit, PR, and release rules for GitHub repositories.

Community
Intermediate
klu-devklu-dev
2

verification-loop

Automate Rust build, lint, test, and security checks with cargo.

Community
Advanced
willyu1007willyu1007

git-commit-conventions

Enforce Git commit message formats, branch naming, and pull request best practices.

Community
Basic