Alex Verkhovsky
eeaaa585ee
* chore(review): swap Augment for Greptile and repair CodeRabbit config Augment is no longer in use, so its guidelines file goes away in favour of greptile.json. Rather than paraphrasing the repo's conventions, both bots are now pointed at the same source files: AGENTS.md and tools/skill-validator.md, plus docs/_STYLE_GUIDE.md scoped to docs. Four CodeRabbit path instructions had gone stale and matched no tracked files: src/**/skills/**, src/**/workflows/**, src/**/tasks/** and src/**/*.agent.yaml. The skill-validator catalog was consequently applied to nothing. Retarget them at src/*-skills/** and src/bmm-skills/agents/**, and drop the two describing layouts the repo no longer has. Three further fixes: `walkthrough: false` is not a schema v2 key, so use collapse_walkthrough; the media filters were root-only globs and left docs/images under review; and the validation-report filter named .md where those files are .html. AGENTS.md gains the prompt-length and testing conventions, which were until now written down nowhere in the repo. CLAUDE.md is unignored and imports it. * chore(review): align catalog scoping and narrow the ignore lists Greptile's global instructions named tools/skill-validator.md and docs/_STYLE_GUIDE.md, but customContext.files supplies those only for skill and documentation paths. Reviewing anything else, Greptile was told to apply catalogs it had not been given — an invitation to invent rules from the filenames. The global clause now names only AGENTS.md, which is loaded on every review; the two scoped catalogs keep their scopes and their own descriptions. website/** was excluding 18 hand-written source files along with the assets — the Astro components and pages, both rehype plugins, the locale and site-url helpers, the i18n JSON. Exclude website/public/** and website/diagrams/** instead, so generated and editor-authored artifacts stay out while the source is reviewed. tools/tests/fixtures/** joins test/fixtures/** ahead of the validator port that moves the skill fixtures there. Those fixtures encode defects deliberately, so any review comment on them is wrong by construction.
1.0 KiB
BMAD-METHOD
Open source framework for structured, agent-assisted software delivery.
Rules
-
Use Conventional Commits for every commit.
-
Before pushing, run
npm ci && npm run qualityonHEADin the exact checkout you are about to push.qualitymirrors the checks in.github/workflows/quality.yaml. -
Skill validation rules are in
tools/skill-validator.md. -
Deterministic skill checks run via
npm run validate:skills(included inquality). -
Documentation conventions are in
docs/_STYLE_GUIDE.md.
Writing prompts
Skills, workflows, tasks, and agent definitions are prompt text that an agent reads in full on every run. Length and ambiguity are paid on every run; a corner case is paid only when it occurs. So do not add instructions for exotic cases — the model usually handles them from context, and the reviewing human can correct it when it does not.
Testing
Automated tests assert outcomes produced by deterministic code. Do not write automated tests for LLM output or for static source text.