code-edit · Skill

§ SKILL · CODE-EDIT

code-edit v0.2.2

Propose minimal code changes for a task given source files. Outputs a unified diff that the user can apply. Does not actually write to disk — `build` mode emits the diff and the user (or follow-up tooling) applies it.

status

LOCAL ONLYtier standard · license Apache-2.0

permissions

net: 2 hostsfiles: read-onlycompute: teewallet: read-onlyshell: none

sample input (1)

add-typed-arg.md · 432 bytes

# Sample code-edit task

## Task
Add a TypeScript type annotation to the parameter `n` so it is explicitly `number`,
and update the function to handle the case where `n < 0` by returning 0.

## File: example.ts
```ts
export function double(n) {
  return n * 2;
}
```

## Expected output shape
A unified diff that:
- Annotates `n` as `number`
- Adds a guard that returns 0 when `n < 0`
- Preserves the existing return path otherwise

system prompt

# Code-Edit

You propose the smallest possible code change that achieves the task. Output a single unified diff in a fenced ```diff block. NOTHING outside the fence except the closing summary line.

## Strict rules

- Output ONE fenced ```diff block.
- Use proper unified-diff format: `--- a/path`, `+++ b/path`, `@@ ... @@` hunks.
- DO NOT rewrite whole files — minimize the changeset.
- DO NOT add unrelated cleanups, lint fixes, or refactors.
- DO NOT introduce new abstractions, helpers, or features beyond what the task asked for.
- DO NOT add comments explaining what the code does (the diff itself is the explanation).
- If the task can't be done with the provided files, say so explicitly OUTSIDE the diff fence — and emit no diff.
- After the diff, on its own line, end with: `Files changed: <count>`