docs(blog): add three articles introducing commit-check#6
Conversation
Add three blog posts for the commit-check site: - One policy file for your Git history (overview / why commit-check) - From zero-config to org-wide policy (configuration & inherit_from) - AI-native: JSON output and a Python API (machine-readable usage) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GDSwJ4o6by3HrzUSzhFLJG
✅ Deploy Preview for commit-check-github-io ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
More reviews will be available in 40 minutes and 33 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThree new blog posts are added under ChangesCommit Check Blog Post Series
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Adds three blog posts to
docs/blog/posts/for the commit-check site.Articles
One policy file for your Git history (
introducing-commit-check.md)— overview of commit-check as a lightweight policy engine for Git
metadata; one
cchk.toml, enforced across CLI / pre-commit / CI; zero-configdefaults and the enabled badge.
From zero-config to org-wide policy (
configuring-commit-check.md)— configuration priority (CLI args →
CCHK_*env → config file), a realcchk.toml, SchemaStore IDE autocompletion, CLI/env overrides,inherit_fromfor org-wide config, andpre-pushforce-push safety.AI-native: JSON output and a Python API (
ai-native-commit-check.md)—
--format jsonstructured output witherror/suggestfor agentself-correction,
--no-banner/--compactquieter modes, and thecommit_check.apiPython interface.All content is drawn from the current project README and
cchk.toml. Each postuses the existing blog frontmatter format (date, categories, tags, author
shenxianpeng).🤖 Generated with Claude Code
Generated by Claude Code
Summary by CodeRabbit
cchk.tomlwith sharing via inheritance.--format jsonstructured output and an in-process Python API.