Skills git-workflow-enforcer

📦

git-workflow-enforcer

Name: git-workflow-enforcer
Author: CrazyDubya

Content revision r1 High Risk ⚙️ External commands📁 Filesystem access🔑 Env variables

Enforce Consistent Git Workflows

Teams often lose time to unclear commits, inconsistent branch names, and incomplete pull requests. This skill provides repeatable Git workflow guidance for Claude, Codex, and Claude Code.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "git-workflow-enforcer" from https://skillstore.io/skills/crazydubya-git-workflow-enforcer.md and its manifest at https://skillstore.io/api/skills/crazydubya-git-workflow-enforcer/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/crazydubya-git-workflow-enforcer.md Signed manifest GET /api/skills/crazydubya-git-workflow-enforcer/manifest Signed lockfile GET /api/skills/crazydubya-git-workflow-enforcer/lockfile

Test it

Using "git-workflow-enforcer". Prepare a commit for fixing a failed login state.

Expected outcome:

A Conventional Commit subject for authentication, plus body notes for user impact, validation steps, and the related ticket.

Using "git-workflow-enforcer". Create a pull request checklist for an API change.

Expected outcome:

A pull request template with description, change type, testing notes, reviewer checklist, warning checks, and related issue fields.

Using "git-workflow-enforcer". Review recent commits before a release.

Expected outcome:

A short workflow report covering commit format drift, missing issue references, release note readiness, and suggested cleanup steps.

Security Audit

High Risk

v8 • 7/5/2026 Open versioned report

Most static external-command alerts are Markdown formatting false positives. The confirmed risks are local Git hook templates and a global Git configuration command that points to ~/.gitmessage. No prompt injection or credential exfiltration intent was found.

Files scanned

216

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

SKILL.md:207-209

Global Git Configuration Change

The skill recommends setting a global commit template that points to ~/.gitmessage. This changes user-level Git behavior beyond the current project.

The lines explicitly show a global Git configuration command with a home-directory template path. The persistence and cross-repository scope are clear.

Medium

SKILL.md:116-149

Persistent Git Hook Templates Execute Local Commands

The skill includes pre-commit and commit-msg hook templates that run local commands during future commits. This is expected for workflow enforcement but requires user consent.

The hook sections include shell shebangs and commands for linting, tests, diffs, and commit message validation. They are presented as templates rather than hidden behavior.

Capability review items (4)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

SKILL.md:209

Hidden file in home directory

git config --global commit.template ~/.gitmessage

Line 209 uses git config --global with ~/.gitmessage, which changes global Git behavior and references a hidden home file. This persists outside the current repository.

High

SKILL.md:209

Hidden file access

git config --global commit.template ~/.gitmessage

Line 209 points Git at ~/.gitmessage, a hidden file in the user home directory. The access is intentional but affects user-level Git configuration.

Medium

SKILL.md:120

Unix shell invocation

#!/bin/sh

The skill provides a pre-commit hook with a /bin/sh shebang that can run npm and git commands if installed. This is legitimate workflow tooling, but it is a real external-command capability.

Medium

SKILL.md:138

Unix shell invocation

#!/bin/sh

The skill provides a commit-msg hook with a /bin/sh shebang that runs during commits if installed. It is expected for Git validation, but it persists as local command execution.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/crazydubya-git-workflow-enforcer/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/crazydubya-git-workflow-enforcer/security.svg)](https://skillstore.io/skills/crazydubya-git-workflow-enforcer?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/crazydubya-git-workflow-enforcer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crazydubya-git-workflow-enforcer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/crazydubya-git-workflow-enforcer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

CrazyDubya. (2026). git-workflow-enforcer security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crazydubya-git-workflow-enforcer/audits/8

BibTeX citation

@techreport{crazydubya-crazydubya-git-workflow-enforcer-2026,
  author = {CrazyDubya},
  title = {git-workflow-enforcer security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/crazydubya-git-workflow-enforcer/audits/8},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "git-workflow-enforcer security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "CrazyDubya"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/crazydubya-git-workflow-enforcer/audits/8"
identifiers:
  - type: other
    value: "skillstore:crazydubya-git-workflow-enforcer:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Standardize Team Commits

Define commit message, branch, and pull request conventions before a shared release cycle.

Prepare Repository Templates

Draft a pull request template, commit message template, and hook guidance for a new project.

Review Release Readiness

Check recent commits and branch names before generating release notes or opening a merge request.

Try These Prompts

Create a Commit Message

Help me write a Conventional Commits message for these changes: [describe the change]. Include a short subject and optional body.

Name a Branch

Suggest a branch name for this task: [task summary]. Use the project convention if one exists.

Draft a Pull Request Template

Create a pull request template for this repository. Include description, change type, testing, checklist, and related issues.

Audit a Git Workflow

Review this repository workflow for commit, branch, hook, PR, and changelog practices. Identify gaps and propose safe improvements.

Best Practices

Review existing repository conventions before proposing new rules.
Ask before creating hooks or changing Git configuration.
Keep commit subjects short, imperative, and tied to one logical change.

Avoid

Do not rewrite team conventions without maintainer approval.
Do not install Git hooks that run commands without review.
Do not treat simple keyword checks as complete secret scanning.

Frequently Asked Questions

Does this skill make commits automatically?

No. It guides commit messages and workflow files. The user or agent must still choose when to commit.

Can it enforce branch protections on GitHub?

It can recommend branch protection settings. It does not change remote repository settings by itself.

Does it support Conventional Commits?

Yes. It uses Conventional Commits types, optional scopes, short subjects, bodies, and issue references.

Can it create pull request templates?

Yes. It provides a standard pull request template structure with testing and review checklist sections.

Are the Git hook examples safe to install?

They should be reviewed first. Hooks can run local commands during commits and may affect developer workflows.

Does it detect leaked secrets?

It includes a simple keyword check example. Use a dedicated secret scanner for reliable detection.

Developer Details

Author

CrazyDubya

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/CrazyDubya/claude-skills/tree/main/git-workflow-enforcer

Ref

02f077c174c5335e2f5d02ca15e77b70d9543e58

Maintenance freshness

7/18/2026

Usage

5 downloads · 227 views

File structure

📄 SKILL.md

git-workflow-enforcer

Install with my Agent

Agent-readable resources

Test it

Security Audit

Confirmed security concerns (2)

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Skillstore Score

What You Can Build

Standardize Team Commits

Prepare Repository Templates

Review Release Readiness

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details