Skip to content

feat: add AGENTS.md, demo GIF, Smithery config, and README refresh#10

Open
shenxianpeng wants to merge 1 commit into
mainfrom
feature/mcp-ecosystem-readiness
Open

feat: add AGENTS.md, demo GIF, Smithery config, and README refresh#10
shenxianpeng wants to merge 1 commit into
mainfrom
feature/mcp-ecosystem-readiness

Conversation

@shenxianpeng
Copy link
Copy Markdown
Member

@shenxianpeng shenxianpeng commented May 26, 2026

Summary

This PR positions commit-check-mcp for the MCP ecosystem explosion by adding:

1. AGENTS.md — AI Agent Instructions

The key differentiator vs commitlint. Tells AI coding agents (Claude Code, Cursor, Copilot, etc.) how to use commit-check-mcp tools effectively. Documents:

  • What each tool does from an agent perspective
  • When to call each tool (before committing, before branching, on first entering a repo)
  • How to interpret structured pass/fail responses
  • Best practices for AI agents

2. Demo GIF

Terminal demo generated with vhs, showing all validation tools in action:

  • Server health check
  • Commit message validation (pass & fail with suggestions)
  • Branch name validation
  • Author info validation
  • Push safety
  • Combined context validation

3. smithery.yaml

Configuration for the Smithery MCP server registry. Allows users to install via npx @smithery-ai/cli install commit-check-mcp.

4. README Refresh

  • AI-agent-first positioning in the header
  • Comparison table: commitlint vs commit-check-mcp (highlighting the unique angle)
  • Smithery badge and installation section
  • Demo GIF at top
  • AGENTS.md reference for AI agents
  • Development / demo regeneration section

Why this matters

The MCP ecosystem is exploding right now. commitlint is designed for human CI pipelines — this tool is uniquely positioned as the first commit validation tool built for AI agents via MCP.

Getting listed on Smithery/mcp.so early provides organic discovery during this ecosystem growth window.

Files changed

File Change
AGENTS.md New — AI agent usage instructions
smithery.yaml New — Smithery registry config
demo/demo.py New — full demo script
demo/demo-compact.py New — GIF-optimized demo
demo/demo.tape New — vhs recording tape
demo/demo.gif New — rendered demo (194KB, 400×400)
README.md Modified — major refresh

Summary by CodeRabbit

  • Documentation

    • Added AI agent integration guide for developers using the toolset
    • Enhanced README with Smithery installation instructions and development section
  • New Features

    • Enabled MCP server integration via Smithery for easier deployment
    • Added terminal demonstration scripts to showcase validation workflows

Review Change Stack

- Add AGENTS.md with AI agent instructions for using commit-check-mcp tools
- Add smithery.yaml for Smithery AI MCP directory listing
- Add demo/demo.py (full) and demo/demo-compact.py (GIF-optimized)
- Add demo/demo.tape and demo/demo.gif (vhs-generated terminal demo)
- Rewrite README with AI-agent-first positioning, comparison to commitlint,
  Smithery badge, demo GIF, AGENTS.md reference, and development section

Positioning: commit-check-mcp is the first MCP-native commit validation tool
designed for AI coding agents, not human CI pipelines.
@github-actions github-actions Bot added documentation Improvements or additions to documentation enhancement New feature or request labels May 26, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 26, 2026

📝 Walkthrough

Walkthrough

This PR adds AI-agent documentation, Smithery integration, and interactive terminal demos to the commit-check-mcp repository. It provides instructions for agents, updates the README with Smithery badge and installation guidance, registers the server with Smithery.ai, and includes executable demos showcasing all validation features.

Changes

Documentation, Smithery Integration, and Demo Implementation

Layer / File(s) Summary
AI Agent documentation and README updates
AGENTS.md, README.md
AGENTS.md provides end-to-end instructions for AI agents on MCP client setup, tool selection, response interpretation, config precedence, and best practices. README header adds AI-agent positioning with Smithery badge, installation via Smithery, Development section with test/demo commands, and License section.
Smithery MCP server configuration
smithery.yaml
Smithery.ai MCP server config declares stdio transport, tool-only capabilities (resources/prompts disabled), and Git/validation/CI metadata tags for registry discovery and client installation.
Terminal demo implementation
demo/demo.py, demo/demo-compact.py, demo/demo.tape
demo.py provides full-featured colored terminal demo with ANSI output helpers and exercises all validation functions (server_health, message/branch/author/push validation, merged config inspection). demo-compact.py offers a minimal variant. demo.tape records a terminal GIF via asprinx recording.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

A README now glows with Smithery pride,
Agents receive clear guidance as their guide.
Demos dance in colors across the terminal screen,
Validating commits with tools so keen. 🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the four main additions: AGENTS.md documentation, demo assets (GIF), Smithery config, and README refresh, which align with the changeset.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/mcp-ecosystem-readiness

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66.02%. Comparing base (880eadf) to head (a6749c6).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #10   +/-   ##
=======================================
  Coverage   66.02%   66.02%           
=======================================
  Files           2        2           
  Lines         209      209           
=======================================
  Hits          138      138           
  Misses         71       71           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@demo/demo.py`:
- Around line 159-160: The two print statements using unnecessary f-strings
(print(f"  AI agents to validate commits, branches, authors,") and print(f" 
push safety, and repository state.")) should be changed to plain string literals
by removing the leading "f" so they are print("  AI agents to validate commits,
branches, authors,") and print("  push safety, and repository state."); locate
and update these exact print calls in demo.py.

In `@README.md`:
- Line 16: The heading "### Why this vs commitlint?" is incorrectly h3 and
should be h2 to preserve Markdown hierarchy; change that line to "## Why this vs
commitlint?" (update the heading level for the heading text "Why this vs
commitlint?") so the document flows from h1 to h2 properly and maintains
accessibility and structure.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 19233b6a-f026-4504-a9de-56f51b71298d

📥 Commits

Reviewing files that changed from the base of the PR and between 880eadf and a6749c6.

⛔ Files ignored due to path filters (1)
  • demo/demo.gif is excluded by !**/*.gif
📒 Files selected for processing (6)
  • AGENTS.md
  • README.md
  • demo/demo-compact.py
  • demo/demo.py
  • demo/demo.tape
  • smithery.yaml

Comment thread demo/demo.py
Comment on lines +159 to +160
print(f" AI agents to validate commits, branches, authors,")
print(f" push safety, and repository state.")
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove unnecessary f-string prefixes.

These f-strings contain no placeholders and should be regular strings.

🧹 Proposed fix
-    print(f"  AI agents to validate commits, branches, authors,")
-    print(f"  push safety, and repository state.")
+    print("  AI agents to validate commits, branches, authors,")
+    print("  push safety, and repository state.")
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
print(f" AI agents to validate commits, branches, authors,")
print(f" push safety, and repository state.")
print(" AI agents to validate commits, branches, authors,")
print(" push safety, and repository state.")
🧰 Tools
🪛 Ruff (0.15.14)

[error] 159-159: f-string without any placeholders

Remove extraneous f prefix

(F541)


[error] 160-160: f-string without any placeholders

Remove extraneous f prefix

(F541)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@demo/demo.py` around lines 159 - 160, The two print statements using
unnecessary f-strings (print(f"  AI agents to validate commits, branches,
authors,") and print(f"  push safety, and repository state.")) should be changed
to plain string literals by removing the leading "f" so they are print("  AI
agents to validate commits, branches, authors,") and print("  push safety, and
repository state."); locate and update these exact print calls in demo.py.

Comment thread README.md

**commit-check-mcp** is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server that exposes [commit-check](https://github.com/commit-check/commit-check) validations as structured tools. AI agents call these tools to validate commit messages, branch names, author info, push safety, and repository state — every tool returns pass/fail results with actionable suggestions.

### Why this vs commitlint?
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix heading level to maintain proper document structure.

The heading jumps from h1 to h3, skipping h2. For correct Markdown hierarchy and accessibility, this should be an h2 heading.

📝 Proposed fix
-### Why this vs commitlint?
+## Why this vs commitlint?
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Why this vs commitlint?
## Why this vs commitlint?
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)

[warning] 16-16: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 16, The heading "### Why this vs commitlint?" is
incorrectly h3 and should be h2 to preserve Markdown hierarchy; change that line
to "## Why this vs commitlint?" (update the heading level for the heading text
"Why this vs commitlint?") so the document flows from h1 to h2 properly and
maintains accessibility and structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants