From 84243cec3dac037a67ebee3331de45702b06d5a5 Mon Sep 17 00:00:00 2001 From: Christian Fehmer Date: Wed, 28 Oct 2026 17:50:56 +0100 Subject: [PATCH] docs: CONTRIBUTING.md to AGENDS.md (@fehmer) --- AGENTS.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index d59a7f8041bb..21ae9c5c3e9d 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -8,4 +8,5 @@ Coding standards (styling, icons, refs, modals) for writing and reviewing code: Before any browser testing, read `docs/AGENT_BROWSER.md` (dev server, `window.__mt` debug handle, gotchas). Roadmap steps (C1, EP1…): `docs/specs/solid-monkeytype/roadmap.md`. Done = tests, lint and a browser check; behaviour changes outside the agreed plan: ask first. Tick the row as "Done in [commit or PR link]: " (PR: add the link in a follow-up commit once it's open), then update rows that cite it. In a git worktree, run `scripts/setup-worktree.sh` before building or testing; there, pnpm tries to reinstall unless `pnpm_config_verify_deps_before_run=false` is set, else run tools via `node_modules/.bin/`. -In plan mode, before writing up a plan, ask clarifying questions if needed. At the end of plan mode, give me a list of unresolved questions to answer, if any. Make them concise. \ No newline at end of file +In plan mode, before writing up a plan, ask clarifying questions if needed. At the end of plan mode, give me a list of unresolved questions to answer, if any. Make them concise. +Before creating a PR, read `docs/CONTRIBUTING.md` and follow the naming conventions