Standards & Conventions

Write the standard once. Every agent follows it.

Your team already writes standards for its coding agents. Baz turns them into requirements verified on every change, and keeps them true as the code moves.

Skills MaintainerActivate
$182 / $10,000
0 PRsView PRs
0 files changed
Manage usage limit in Account settings

Skills scan

Control when scans are activated

Select the repositories you want to include in the skills scan
Select repositoriesScan now
Enable scheduled scan
Save

Configure PR conventions for the Skills Maintainer

Control how skill maintenance PRs are created, including limits, titles, and branch names

Max open fix PRs Limit the number of open PRs created by the agent at any given time

Set

PR title prefix Applied to all Skills Maintainer-generated PR titles

Set

PR branch prefix Applied to all Skills Maintainer-generated branch names

Set

How Baz makes agents steerable

Write the guidance once. Baz carries it into planning, enforces it in review, and keeps it current.

  1. WriteCLAUDE.md, AGENTS.md, Cursor rules, and Skills you already keep
  2. PlanThe plugin carries them into Claude Code, Codex, and Cursor
  3. EnforceAI Coding Guidelines verifies every change, citing the rule
  4. LearnMemory and custom reviewers capture repeated feedback
  5. MaintainSkills Maintainer opens a PR when a rule drifts

AI Coding Guidelines

Applies the rules from AGENTS.md, CLAUDE.md, Cursor rules, and Skills that cover the changed files, and cites the file.

Skills Maintainer

Opens a pull request when a rule stops matching the code.

Fix the rule, not just the code

Reply "fix skills" on a finding and Baz updates the instruction file in its own PR.

Reviewer memory

Say it twice and the reviewer adapts. Memories are versioned and revertible.

Standards before the code

The Baz plugin brings the same rules into Claude Code, Codex, and Cursor.

Awesome Reviewers

An open library of review instructions from real discussions, ready to drop into a Skill.

What steering looks like on a real repository

Each of these is a standard that would otherwise live in someone's head or drift silently.

A rule the code outgrew

Situation CLAUDE.md requires getAuthorizedUser; auth moved to middleware.

Baz does Skills Maintainer opens a PR to rewrite the rule.

A path that moved

Situation A rule points to an import path that was split.

Baz does Review cites the rule, and the file gets a matching update.

Feedback repeated every week

Situation Reviewers keep asking for the same retry wrapper.

Baz does Memory learns it the second time.

A rule for one corner of a monorepo

Situation Migrations have conventions the frontend does not share.

Baz does A scoped AGENTS.md applies only under its directory.

From suggestions to a standard

Instruction files aloneStandards in Baz
Agents follow them on a best-effort basisEvery change is verified against the rules in scope
The same intent copied across five tool formatsOne set of files, discovered across every format
Rules drift silently as the code movesSkills Maintainer opens a PR when a rule stops holding
Reviewers repeat the same feedbackMemory and custom reviewers learn it once

Questions teams ask first

Does Baz replace CLAUDE.md or AGENTS.md?

No. Baz reads the files you already keep and enforces them.

What about personal rules and agent memory?

Baz enforces what lives in your repositories. Team-wide rules belong there.

What does Skills Maintainer need?

Write access. It runs on a schedule or on demand, within a PR cap and your usage limit.

Make your instruction files a standard

Connect a repository and Baz picks up the guidance already in it. Want help consolidating rules across tools? Talk to us.