القائمة
The full procedure for adding a bytecode instruction to Grob — touch the enum, the compiler selection logic and the VM dispatch together, with stability rules.
التثبيت باستخدام 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 | Adding an OpCode |
| description | The full procedure for adding a bytecode instruction to Grob — touch the enum, the compiler selection logic and the VM dispatch together, with stability rules. |
The OpCode enum is meant to be complete from Sprint 2 and not grown casually. Adding
one is a deliberate, decision-logged act governed by ADR-0013 (opcode stability). Reach
for this skill only when a genuinely new bytecode instruction is required by a feature
in scope — not to optimise an existing sequence without a decision behind it.
An opcode lives in three places that must change together. Changing one or two and not the third is the classic miscompilation: the compiler emits something the VM cannot decode, or the VM has a handler nothing emits.
D-### or an acceptance criterion that needs this instruction? If not,
this is a design decision, not an implementation task. Stop and raise it.&&
and || short-circuit via jumps; compound assignment desugars to load-operate-store.
Do not add an opcode for something the compiler can already lower..grobc wire
format (grob-grobc-format.md); adding one has versioning implications.Grob.Core)Add the case to OpCode : byte in Grob.Core, in the correct category section
(Values, Arithmetic, Comparison, Logic, Variables, Upvalues, Properties, Array, Control
flow, Functions, Structs, I/O, Increment/decrement, Nil, String interpolation, Exception
handling, Module). Document the operand layout in a trailing comment exactly as the
existing cases do — operand byte count and meaning. The OpCode enum is the single
source of truth for the instruction set.
Grob.Core)If the opcode carries operands, make sure the chunk's write and read helpers handle the operand width. Keep the line-number array in step — every emitted instruction records its source line in the parallel array, never inline.
Grob.Compiler)In the compiler visitor pass, emit the opcode where the type-annotated AST calls for it.
If the opcode is one of a typed family (the Int / Float / String split), the
selection is driven by the ResolvedType the type checker set — there is no runtime
type check, so the compiler must pick correctly here. Add the selection to the right
partial-class file by concern.
Grob.Vm)Add the handler to the fetch/decode/execute switch in VirtualMachine. Decode operands
with the same width the compiler wrote. Implement the stack effect precisely: how many
values it pops, how many it pushes. Runtime errors raised here carry the source line
from the chunk's line array and are subtypes of GrobError. The VM stops on the first
runtime error.
Grob.Compiler.Tests: given source that should produce the opcode, assert the exact
emitted bytecode including operands.Grob.Vm.Tests: hand-construct a Chunk using the opcode and assert the execution
result and stack effect.Grob.Integration.Tests case proving it
end-to-end.If this opcode changes the instruction set in a way that affects the .grobc format or
the stability contract, add a decisions-log entry (D-###) and update ADR-0013's
coverage if needed. Reference the D-### in the commit.
Grob.Core)Grob.Compiler)Grob.Vm)dotnet build and dotnet test green