skills.rest
johangm90
johangm90COMMUNITY
Explore all skills by this author →
GitHub

spex-gitops

Validate commit messages and generate pull request descriptions via gh.

Updated Mar 5, 2026
Search Tags:#git#changelog#conventional commits#branching#pull requests#repository hygiene
One-click install
npx skills add https://github.com/johangm90/spex --skill spex-gitops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spex-gitops
Source: https://github.com/johangm90/spex/tree/main/skills/spex-gitops
Command: npx skills add https://github.com/johangm90/spex --skill spex-gitops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates repository hygiene, ensuring consistent commit messages, standardized branch naming, and clear pull request descriptions, streamlining collaboration and maintaining a clean project history.

Core Features & Use Cases

  • Commit Message Validation: Enforces Conventional Commits standards, rewriting messages for clarity and compliance.
  • Branch & PR Management: Creates feature branches and generates PR descriptions according to defined policies.
  • CHANGELOG Generation: Automatically drafts entries for release notes based on completed work.
  • Use Case: When you finish a feature, this Skill ensures your commit messages are correctly formatted, your branch name follows the slice/NNN-<slug> pattern, and a well-structured PR description is ready for review.

Quick Start

Use the spex-gitops skill to validate my commit message against conventional commits.

Frequently Asked Questions about spex-gitops

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

FAQPage Schema
How do I enforce conventional commits formatting in my git repository?▼

Conventional commits formatting is enforced through automated validation that checks commit messages against the standard, rewriting them for clarity and compliance to maintain repository hygiene.

How do I automatically generate pull request descriptions from my branch names?▼

Pull request descriptions are generated automatically by enforcing a standardized branch naming policy using the slice/NNN-slug pattern, then submitting the PR via the gh command line tool.

What is the best way to maintain a Keep-a-Changelog standard for release notes?▼

The best way to maintain Keep-a-Changelog standards is by automatically drafting new entries based on completed work, ensuring release notes accurately reflect repository history.

Do I need the spex agent framework to manage branch creation and repository hygiene?▼

Yes, the spex agent framework is required as the Skill operates within it, utilizing MCP for state management to adhere to strict git workflows and branching policies.

Why should I use automated repository hygiene instead of manual git workflow enforcement?▼

Automated repository hygiene ensures consistent commit messages, standardized branch naming, and clear pull request descriptions, streamlining collaboration and maintaining a clean project history without manual overhead.

Related Skills

Explore More Software Engineering Skills→
JordiNodeJSJordiNodeJS

github-pull-request

Automate GitHub pull request creation, updates, merging, and release tagging via GitHub CLI.

Community
Advanced
pacaplanpacaplan
30

release

Create release pull requests with semantic version bumps and changelog entries.

Community
Advanced
YoshikemoloYoshikemolo
5

git-jira-integration

Generate Git branch names and validate commit messages against Jira issues.

Community
Intermediate
kenkenmainkenkenmain
1

gh-repo-setup

Automate GitHub repository setup with GitFlow, branch protection, templates, and CI.

Official
Advanced