القائمة
How to add an entry to the Grob decisions log in the established ADR style, keep the index and changelog in lockstep, and maintain supersession links.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Syntax, idioms and conventions for writing .grob programs — sample scripts, integration-test fixtures, error examples. Use this skill whenever you create or edit a .grob file, so the language source is idiomatic and valid against the v1 surface. Covers bindings, the three string forms, nullability, control flow, lambdas, collection pipelines, structs, errors, the stdlib surface and numerics.
The single authoritative procedure for allocating a Grob error code — the pre-declared-budget model with an allocate-and-surface fallback for the unanticipated case. Use whenever an increment needs a diagnostic code: to confirm the budget covers it, to make the fold-into-existing versus register-new judgement, or to register a new code in lockstep. Codes are immutable once shipped (ADR-0017), so this keeps the design judgement explicit while making the mechanics deterministic. writing-an-error-test defers to this skill for the code itself.
Use when an increment introduces, resolves or constructs a Grob type — a `type` declaration, a struct construction, an anonymous struct, a new type-annotation position, a new built-in type, or any feature where a value carries a type the checker must resolve and the VM must represent. Encodes the four failure modes that produced the Sprint 5 post-close interludes (type-reference-grammar gaps, conflated cycle walks, non-uniform redeclaration and lifecycle objects escaping through new containers) as a standing pre-flight and a closing checklist. Reuses, does not replace, `adding-an-opcode` and `tdd-cycle`.
The sanctioned procedure for adding a parser production or an AST node to Grob — the parser/AST analogue of adding-an-opcode. Use when an increment genuinely needs a new surface form or a new node that is not already there (a new construction expression, a new literal, a new annotation position). The front end is built incrementally, so this is a real and expected job — not a wall to route around with an improvised gap-fix. It is deliberate and reviewable, never silent.
How to add or update a gold-master error-example pair (_grob.txt + _expected.txt) and register the error code, without breaking the negative-test release gate.
Use during a manual PR review to pull SonarQube Cloud (SonarCloud) findings for the pull request straight from the Web API — issues on new code, the quality-gate verdict and the new-code coverage against the floor — without the Docker-based Sonar MCP server. Produces a compact findings block for the reviewer to fold into its PR comment. It does not post anything; the human composes and posts the comment. Assumes the PR's Sonar scan has already completed (the reviewer is triggered manually after all scans).
| name | Logging a Decision |
| description | How to add an entry to the Grob decisions log in the established ADR style, keep the index and changelog in lockstep, and maintain supersession links. |
docs/design/grob-decisions-log.md is the authority for the whole project. When a
design decision is made — a feature shaped, an open question closed, a previous decision
changed — it is captured here as a numbered D-### entry. This skill is for adding one
correctly. Note: deciding what the decision is belongs to the maintainer; this skill
is about recording a decision that has been made, in the right form.
OQ-###) being resolved — the entry closes it and the open-questions
doc is updated to point at the resolving D-###.Match the existing entries exactly. The shape is:
### D-### — Short title (Month Year)
Area: <the subsystem or concern>
Supersedes: <D-### or none>
Superseded by: <D-### or none>
<Short prose body. State the decision first, plainly. Then the rationale —
why this and not the alternatives. Point at the spec doc that carries the
full detail rather than reproducing it here. Keep it tight; the log is a
record of decisions, not a spec.>
-----
D-### in sequence. Check the tail of the file for the
current highest.Area is a short noun phrase naming the subsystem (VM — value representation,
Control flow — select exhaustiveness).A decisions-log change touches three places in the same edit:
If you close an open question, also update grob-open-questions.md so the question
moves from open to resolved with a pointer to the D-###.
When D-new supersedes D-old:
D-new gets Supersedes: D-old.D-old gets Superseded by: D-new.Both ends. A one-way link is a defect that misleads the next reader. If an ADR in
docs/wiki/ADR/ is affected (as ADR-0016 was superseded by D-288 and D-291), note it
there too and in Home.md.
Per the project's working pattern, deliver the full updated grob-decisions-log.md, not
a diff or a patch. Every session output is a complete, ready-to-use file.
D-### used; format matches existing entries exactlygrob-open-questions.md updated if an OQ-### is closedHome.md updated if applicable