cog-commit

Generate Conventional Commits with memory context and secret guards.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/bketelsen/max --skill cog-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cog-commit
Source: https://github.com/bketelsen/max/tree/main/skills/cog-commit
Command: npx skills add https://github.com/bketelsen/max --skill cog-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the creation of git commit messages that reference memory context and rationale, helping changes stay traceable and better understood later.

Core Features & Use Cases

  • Memory-context aware commits: generate messages that reference relevant memory fragments to justify changes.
  • Guardrails and safety: avoid committing secrets or build artifacts, and follow Conventional Commits format for consistency.
  • Workflow integration: works with staged changes and can accompany documentation updates or refactors.

Quick Start

Ask me to commit your current changes with memory-context-aware notes.

Frequently Asked Questions about cog-commit

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

FAQPage Schema
How do I generate git commit messages with memory context?▼

To generate git commit messages with memory context, you stage your changes and prompt the skill to commit. It references relevant memory fragments to justify modifications, producing a concise subject line and optional body.

Can I enforce conventional commits format automatically for my repository?▼

Yes, you can enforce conventional commits automatically. The skill applies the Conventional Commits format to your staged changes, ensuring consistent version-control history while generating a concise subject line and optional descriptive body.

How do I guard against committing secrets and build artifacts in git?▼

To guard against committing secrets and build artifacts, the skill includes built-in safety guardrails. It automatically scans your staged changes to prevent sensitive data and unnecessary artifacts from entering your version-control history.

What is the best way to link memory notes to git commits for better traceability?▼

The best way to link memory notes to git commits is using memory-context aware generation. The skill crafts messages that reference relevant memory fragments and user intent, improving traceability, accountability, and future context for code changes.

Do I need staged changes to use memory-aware git commits?▼

Yes, you need staged changes to use memory-aware git commits. The skill integrates with your existing workflow by processing currently staged changes to generate the conventional commit message with appropriate memory context references.