Menu

Individual skill

ai-coding-guardrails

0upvotes

Use when an AI coding agent is writing or refactoring production code and its known failure modes need to be held in check — over-engineering, silent scope creep, invented APIs, claiming work is done without checking, deleting tests to make them pass. Trigger when the user asks for careful, production-grade, or reviewed code, or when a previous agent run produced confident output that turned out wrong.

ai-coding-guardrails/SKILL.md

Read pinned source

Source commit b2267d9171af4f56848d82992381b20b89b44056

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
425
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# AI Coding Guardrails

Coding agents fail in a small number of predictable ways. This is the checklist that catches them before the diff lands.

## The Rules

**1. Match the codebase, not your preferences.**
Read two or three neighbouring files before writing. Use the project's existing patterns, naming, error handling, and comment density — even when you would have done it differently. A diff that reads like the rest of the repo is the goal. Introducing a new pattern is a decision the user makes, not a default.

**2. Change the smallest thing that works.**
No speculative abstraction. No config option nobody asked for. No "while I was in here" rewrite. If a fix is three lines, the diff is three lines. Refactors ride separately from behavior changes so a reviewer can see one thing at a time.

**3. Never invent an API.**
If you cannot see a function's signature in the repo, in installed source, or in the documentation, do not call it. Grep for it first. A plausible-looking method that does not exist is the single most common way agent code fails, and it fails at runtime, in front of the user.
Back to top