blog-git-commit

Standardize blog commits with typed messages and staged-change validation.

1|5|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/mdproctor/cc-praxis --skill blog-git-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog-git-commit
Source: https://github.com/mdproctor/cc-praxis/tree/main/blog-git-commit
Command: npx skills add https://github.com/mdproctor/cc-praxis --skill blog-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blog repositories often suffer from inconsistent commit messages that hamper readability and collaboration. This skill enforces blog-specific commit conventions to keep history clear and reviewable across posts, drafts, assets, and configuration changes.

Core Features & Use Cases

  • Enforces blog-type commit messages (post, edit, draft, asset, config) tailored for GitHub Pages / Jekyll blogs.
  • Guides scope selection and subject length to improve traceability and review efficiency.
  • Provides a deterministic workflow for staged changes, validation, and suggested messages.

Quick Start

Stage your blog changes and apply the blog-git-commit workflow to produce consistent, descriptive commit messages.

Frequently Asked Questions about blog-git-commit

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

FAQPage Schema
How do I standardize git commit messages for a Jekyll blog repository?

Standardize git commit messages for a Jekyll blog by applying deterministic workflows with blog-specific commit types like post, edit, draft, asset, and config. This ensures clear, reviewable history across your content repository.

What are conventional commits for blog content management and why use them?

Conventional commits for blog content management categorize changes into types like post, draft, and config to improve traceability and review efficiency. They solve inconsistent commit messages that hamper readability and collaboration in blog repositories.

Can I use this commit workflow for GitHub Pages configuration and asset changes?

Yes, this commit workflow supports GitHub Pages configuration and asset changes. It guides scope selection and subject length for assets and configuration updates, ensuring every staged change follows clear conventions for better traceability.

What's the best way to validate staged blog changes before committing?

Validate staged blog changes before committing by applying a deterministic workflow that checks staged files and suggests descriptive commit messages. This staged-change validation ensures your blog history remains clear and reviewable.

Does this blog commit convention work without any extra dependencies?

Yes, this blog commit convention works without any extra dependencies. It imposes commit types and subject-length guidelines directly on your Git-based workflow, requiring no additional components or plugins to standardize your blog repository history.