deviation-reporting

Rules for classifying and reporting deviations from a plan during implementation — breaking deviations require user approval, trivial deviations are…

Skill by MoltenRuby

IndexedMIT

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/moltenruby-deviation-reporting

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Rules for classifying and reporting deviations from a plan during implementation — breaking deviations require user approval, trivial deviations are self-executed and logged in a structured report at the end

Use cases: documents

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/deviation-reporting

What's inside

Skill name: deviation-reporting
Description: Rules for classifying and reporting deviations from a plan during implementation — breaking deviations require user approval, trivial deviations are self-executed and logged in a structured report at the end
License: MIT
Compatibility: opencode
Instructions: 25 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

## Deviation rules

When following a plan, you may encounter opportunities to improve or cases where the plan is suboptimal.

**Before deviating, classify the deviation:**

- **Breaking deviation** — the change could break subsequent plan steps, introduce a logic inconsistency, change a public interface or exported symbol, alter data structures other code depends on, or have non-obvious downstream effects.
  - **Stop and ask the user** before implementing. State clearly: what you want to change, why, and what the risk is. Wait for approval.

- **Trivial deviation** — the change is purely local (e.g. a naming improvement, an idiomatic rewrite of a single expression, adding a missing error check or type annotation, extracting a small helper that does not change any interface). Subsequent steps are unaffected or can be trivially adjusted.
  - **Implement without asking.** Record the deviation for the final report.

**At the end of every implementation**, if any trivial deviations were made, append a numbered list in this exact format:

```
## Deviations from plan

DEVIATION-1: <what was changed> — <reason>
DEVIATION-2: <what was changed> — <reason>
...
```

If no deviations were made, omit the section entirely.

From MoltenRuby/MrSmith, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Mar 21, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/MoltenRuby/MrSmith
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from MoltenRuby

Cite this page

deviation-reporting skill. Agent Mart. https://agentmart.dev/skills/moltenruby-deviation-reporting (last updated 2026-10-24)