reset-code

Reset generated code and workflow data to restore a plugin's pristine state.

14|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/brsbl/ottonomous --skill reset-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reset-code
Source: https://github.com/brsbl/ottonomous/tree/main/.claude/skills/reset-code
Command: npx skills add https://github.com/brsbl/ottonomous --skill reset-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reset project data to restore the plugin to a pristine state, removing generated code and workflow data while preserving essential files and history.

Core Features & Use Cases

  • Full reset of the plugin state including code, workflow data, and dependencies, with an allowlist of preserved files.
  • Selective resets by target: diffs, otto, code, deps, or all.
  • Safe-preserve defaults: preserves .claude, .claude-plugin, skills, .git, README, LICENSE, .gitignore, .gitmodules.

Quick Start

Run /reset-code to perform a full reset, or specify a target like diffs, otto, code, or deps to reset specific parts.

Frequently Asked Questions about reset-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reset generated plugin code and revert workflow data to a clean state?

Reset generated plugin code and workflow data by running a full reset command that removes diffs, code, and dependencies while preserving essential files like .git and .claude-plugin, restoring the project to a pristine state.

What's the best way to remove experimental changes from a plugin without deleting configuration files?

Remove experimental plugin changes safely by using a reset tool with an allowlist that preserves essential files such as .claude, skills, README, LICENSE, and .gitignore while clearing all generated artifacts and inconsistent state data.

Can I selectively reset specific parts of a plugin like diffs or dependencies instead of wiping everything?

You can selectively reset specific plugin parts by specifying a target such as diffs, otto, code, or deps, which removes only the chosen data while leaving other workflow components and preserved files intact.

When should I use a full plugin reset versus a targeted dependency cleanup?

Use a full plugin reset when experiments leave code, state, and dependencies in an inconsistent state requiring complete reversion; use a targeted dependency cleanup when only deps need reverting and generated code remains valid.

Why does my plugin end up in an inconsistent state after running experiments?

Plugins end up in an inconsistent state after experiments because generated code, workflow data, and dependency changes accumulate without rollback, requiring a target-based reset to revert changes across code, state, and dependencies.

Does the reset process preserve git history and skill files when restoring a plugin to its pristine state?

The reset process preserves git history and skill files by enforcing a safe-preserve allowlist that retains .git, .gitignore, .gitmodules, skills, .claude, and .claude-plugin while removing all other generated code and workflow data.