You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`validate_branch_name` — validates a branch name or the current repo branch
12
+
-`validate_author_info` — validates author name/email or the repo's git author config
13
13
-`validate_commit_context` — runs combined checks in one call
14
+
-`validate_repository_state` — validates latest commit, current branch, and author state for a repo
15
+
-`describe_validation_rules` — returns the effective config and enabled rules after merging defaults and repo config
14
16
15
17
All validation tools return the same structured commit-check result shape:
16
18
@@ -42,3 +44,28 @@ commit-check-mcp
42
44
```
43
45
44
46
The server runs over stdio transport (recommended MCP default for local tool integrations).
47
+
48
+
## Repository-Aware Validation
49
+
50
+
`commit-check` is most useful when it runs against a real git repository and its `cchk.toml` or `commit-check.toml` file. This MCP server now supports that directly:
51
+
52
+
-`repo_path` — run git-based validations against a specific repository
53
+
-`config_path` — point to an explicit TOML config file; relative paths are resolved from `repo_path`
54
+
-`config` — apply ad-hoc overrides on top of defaults and repo config
55
+
56
+
Typical patterns:
57
+
58
+
- Validate an explicit message with a repository's rules
59
+
- Validate the current repository state without passing message/branch/author values manually
60
+
- Inspect which rules are actually enabled after config merging
0 commit comments