rules SKILL.md skillA

rules from chan4lk/specclaw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add chan4lk/specclaw/rules@git:20261016.229bbe5

Pins git:20261016.229bbe5 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: chan4lk/specclaw
Path: plugins/specclaw-review/skills/rules/SKILL.md
Versions recorded: 1
Latest version: git:20261016.229bbe5, committed Oct 16, 2026
Size: 3,765 bytes
Repository stars: 14
License: MIT

Use when setting up specclaw-review in a repo, when the user wants review rules created or improved, or asks what the reviewer should check in this codebase.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# specclaw-review: create the review rules for this repo

Two outputs:
1. a `review:` block in `.specclaw/config.yaml`;
2. rule files in `.specclaw/review/rules/`.

**Write nothing until the user approves what you show them.** Rules decide what blocks a PR, so a rule written
silently is a gate nobody agreed to.

## 1. Find what the repo already has

Run `specclaw-review discover` (or call the `review_discover` MCP tool). It is read-only and lists:
- the repo's governance by category, with sizes;
- whether those files define severity;
- the existing repo rules;
- how much review history is on disk;
- whether a PR host can be read;
- a suggested `review:` block.

Before you go on:
- **Existing governance wins.** Point `review.governance` at those files; they are read fresh every round. Never
  copy them into rule files, because copies go stale.
- **Decisions/ADRs stay out of the rulebook.** List them for the user. The reviewer reads them with its tools when
  a change touches them.
- **Over budget:** if the inlined size is over budget, propose which files to drop from `governance`, smallest
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add chan4lk/specclaw/rules@sha256:ced0b77329e3cbb4

The line at the top of this page pins the label git:20261016.229bbe5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_f77pudqaunaifxn3.svg)](https://markdownregistry.com/a/art_f77pudqaunaifxn3)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 16, 2026.

version	committed	commit	size	audit
git:20261016.229bbe5 latest	2026-10-16	229bbe5	3,765 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3765 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

chan4lk/specclaw · 14 stars · license MIT · pushed 2026-11-08 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_f77pudqaunaifxn3
GET https://markdownregistry.com/api/v1/resolve?ref=chan4lk/specclaw/rules
GET https://markdownregistry.com/api/v1/blob/ced0b77329e3cbb402cd0a5a2b7c73ec4b037414a9d8a1bd5eedd3331fd23988

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from chan4lk/specclaw

specclaw SKILL.md skill

chan4lk/specclaw · .agents/skills/specclaw/SKILL.md · Run the SpecClaw spec-driven lifecycle in this repository when a request needs proposal, planning, build, verification…

git:20261011.f968269 · audit A · 14 stars

CLAUDE.md CLAUDE.md file

chan4lk/specclaw · CLAUDE.md

git:20261029.e7b3be8 · audit A · 14 stars

llms-full.txt@docs llms.txt file

chan4lk/specclaw · docs/llms-full.txt

git:20261011.f968269 · audit A · 14 stars

llms.txt@docs llms.txt file

chan4lk/specclaw · docs/llms.txt

git:20260717.fc3814b · audit A · 14 stars

bf-analyze SKILL.md skill

chan4lk/specclaw · plugins/specclaw-bf/skills/bf-analyze/SKILL.md · Use when onboarding to an existing or legacy codebase that needs a grounded stack, dependency and risk report.