rulecheck
|
pinned to #6045848updated 3 months ago
Ask your AI client: “install skills/rulecheck”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/rulecheckmetahub onboarded this repo on the author's behalf.
If you own github.com/coleam00/Archon on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
22,840
Last commit
3 months ago
Latest release
published
- #ai
- #automation
- #bun
- #claude
- #cli
- #coding-assistant
- #developer-tools
- #typescript
- #workflow-engine
- #yaml
About this skill
Pulled from SKILL.md at publish time.
Launch the rulecheck-agent to autonomously scan and fix CLAUDE.md rule violations.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.6045848· 3 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
4 passed1 warningDescription qualitywarn
14 words · 97 chars — skills use the description as their trigger; aim higher — manifest description is empty; graded the GitHub repo description instead
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
18,679 chars · 13 sections · 14 code blocks
Tags / topics declared
10 total — ai, automation, bun, claude, cli, coding-assistant (+4)
README has usage / example sections
found: Getting Started
Homepage / docs URL declared
https://archon.diy
Release history
1- releasecurrent6045848warn3 months ago
Contents
Launch the rulecheck-agent to autonomously scan and fix CLAUDE.md rule violations.
Your Job (Main Agent)
You are the orchestrator. Your ONLY job is to launch the rulecheck-agent and report its results when it completes. You do NOT do the scanning or fixing yourself.
- Launch the rulecheck-agent with the focus area (if any):
$ARGUMENTS - Wait for it to complete — do NOT poll, tail, or check on it. You will be notified automatically when it finishes.
- Report ONLY what the agent told you — relay its final message verbatim or summarize it. Do NOT search for PRs, read files, or fabricate results. If the agent hit its context limit, say so. If it didn't produce a PR URL in its output, don't go looking for one.
Rules for You
- Do NOT scan the codebase yourself — that's the agent's job
- Do NOT grep, read source files, or run linters — the agent handles all of that
- Do NOT edit any files — you are the orchestrator, not the fixer
- Do NOT try to resume or check on the agent while it's running — just wait
- Do NOT do the agent's work if it fails or hits context limits — report the failure to the user and stop. NEVER pick up where the agent left off. You are not in a worktree and would be editing main directly.
- Do NOT update project memory — the agent maintains its own memory at
.claude/agent-memory/rulecheck-agent/. Do not duplicate run results into your project memory. - Trust the agent. It runs in an isolated worktree and will create a PR when done.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/rulecheck