cocosearch-commit

Smart Commit with CocoSearch

A structured workflow for generating comprehensive commit messages. Uses CocoSearch's semantic search and dependency analysis to understand what changed, why it matters, and what it affects — producing commit messages that go far beyond surface-level diff summaries.

What this adds over generic commit message generators:

• Semantic understanding: Knows what the changed code does, not just what lines changed
• Blast radius awareness: Flags when changes affect high-impact files with many dependents
• Dependency context: Understands what the changed code relies on
• Cross-cutting synthesis: Detects when changes span multiple subsystems and summarizes coherently
• Conventional Commits: Automatically determines type, scope, and breaking changes

Pre-flight Check

1. Resolve index name (use the resolved name for all operations):

   • Try cocosearch.yaml for indexName field -- if found, use it
   • If no config file, call list_indexes() and match the current project's directory name against available indexes. The MCP tools auto-derive index names from directory paths (e.g., my-project/ -> my_project), so a match is likely if the repo was indexed without a config file.
   • If no match found, the project is genuinely not indexed -- warn: "No CocoSearch index found. I'll generate a commit message from diffs alone, but semantic analysis won't be available. Want me to index first?" Do NOT abandon CocoSearch tools just because cocosearch.yaml is missing.

2. list_indexes() to confirm project is indexed

3. index_stats(index_name="<resolved-name>") to check freshness

   • Stale (>7 days) -> warn: "Index is X days old -- semantic context may not reflect recent changes."

4. Check dependency freshness -- call get_file_dependencies on any known file:

   get_file_dependencies(file="<any-known-file>", depth=1)
   

   • If response contains warnings with type deps_outdated or deps_branch_drift: Note: "Dependency data is outdated -- impact analysis may be incomplete."
   • If response contains warnings with type deps_not_extracted: Note: "No dependency data found. Blast radius analysis will be skipped."
   • If no warnings: Proceed with full analysis.

5. Linked index health (if cocosearch.yaml has linkedIndexes):

   • Check the warnings array from index_stats() for entries starting with "Linked index"
   • If stale/missing: note — "Linked index 'X' is stale/missing. Cross-project context may be limited."