cocosearch-commit

Generate conventional commit messages from staged or unstaged diffs.

37|6|Updated Feb 16, 2026

Search Tags:#automation #commit #diff #conventional-commits #semantic-analysis #coco-search #preflight-check

Ready to run

npx skills add https://github.com/VioletCranberry/coco-search --skill cocosearch-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cocosearch-commit
Source: https://github.com/VioletCranberry/coco-search/tree/main/skills/cocosearch-commit
Command: npx skills add https://github.com/VioletCranberry/coco-search --skill cocosearch-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate conventional commit messages from code changes by analyzing staged (or unstaged) diffs with CocoSearch's semantic search and dependency impact.

Core Features & Use Cases

Semantic understanding of changed code to determine meaningful commit context
Blast radius awareness and impact on dependents
Dependency context to reflect how changes affect dependencies
Cross-cutting synthesis to summarize changes across subsystems
Conventional Commits: auto-detect type, scope, and breaking changes

Quick Start

Provide the changes you want to commit; the tool will analyze diffs and propose a conventional commit message for review.

Frequently Asked Questions about cocosearch-commit

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

FAQPage Schema

How do I generate conventional commit messages from code diffs automatically?▼

You can generate conventional commit messages from code diffs by analyzing staged or unstaged changes with semantic search to determine context, scope, and breaking changes. The tool performs per-file analysis and cross-cutting synthesis to propose a message for review.

What is blast radius analysis in semantic commit generation?▼

Blast radius analysis calculates the dependency impact of your code changes, tracking how modifications affect dependents across subsystems. This awareness ensures the generated conventional commit message accurately reflects the risk and scope of the changes.

How do I detect breaking changes before creating a conventional commit?▼

You can detect breaking changes before committing by running pre-flight checks that analyze staged diffs and calculate dependency impact. This semantic analysis identifies potential breaking changes and prompts for user review before finalizing the commit.

Can I review and approve generated commit messages before committing changes?▼

Yes, an interactive approval flow prompts you to review the proposed conventional commit message before committing. The tool performs pre-flight indexing checks and diff collection, then waits for your explicit approval to ensure accuracy.

Does conventional commit automation work with unstaged changes?▼

Yes, semantic commit generation works with both staged and unstaged diffs. The tool collects the diff, performs per-file analysis to detect type and scope, and synthesizes the results into a conventional commit message for your review.

When should I use semantic analysis for commit messages instead of writing them manually?▼

You should use semantic analysis when you need to summarize cross-cutting changes across multiple subsystems or evaluate dependency impact. It automates conventional commit type, scope, and breaking change detection, which is useful for complex, large-scale modifications.