code

1# Code Harness
2 
3When this skill triggers, call the `code` tool from the `ejentum` MCP server. Pass a 1-2 sentence framing of WHAT you are coding or reviewing as the `query` argument. Include the failure risk to avoid where possible.
4 
5Good query: `review a Python refactor that converts raise UserNotFound to silent default return; tests still pass`
6Bad query: `look at this code`
7 
8The tool returns a structured scaffold containing:
9 
10- `[CODE FAILURE]`: engineering failure pattern to avoid
11- `[ENGINEERING PROCEDURE]`: steps to follow
12- `[REASONING TOPOLOGY]`: decision flow
13- `[CORRECT PATTERN]`: shape correct code should take
14- `[VERIFICATION]`: self-check
15- `Amplify:` and `Suppress:` signals
16 
17Absorb internally. Do NOT echo bracket labels in the user-facing reply. Apply the scaffold's failure-pattern check against your draft before responding; if your code exhibits the named failure, rewrite.
18 
19If the API is unreachable, proceed with native engineering. The scaffold enhances; it is not a hard dependency.
20 
21Latency cost: ~1 second. Benefit: catches the kinds of behavioral changes and silent contract violations that look plausible but break under real conditions.