opencode-froggy 0.7.1 → 0.7.2

package/README.md

@@ -7,7 +7,7 @@
   <a href="https://www.npmjs.com/package/opencode-froggy"><img src="https://badge.fury.io/js/opencode-froggy.svg" alt="npm version"></a>
 </p>
 
-OpenCode plugin providing hooks, specialized agents (architect, doc-writer, rubber-duck, partner, code-reviewer), skills (code-simplify, code-release), and tools (gitingest, blockchain queries, agent-promote).
+OpenCode plugin providing hooks, specialized agents (architect, doc-writer, rubber-duck, partner, code-reviewer, code-simplifier), skills (code-release), and tools (gitingest, blockchain queries, agent-promote).
 
 ---
 
@@ -17,7 +17,6 @@ OpenCode plugin providing hooks, specialized agents (architect, doc-writer, rubb
 - [Commands](#commands)
 - [Agents](#agents)
 - [Skills](#skills)
-  - [code-simplify](#code-simplify)
   - [code-release](#code-release)
 - [Tools](#tools)
   - [gitingest](#gitingest)
@@ -77,6 +76,7 @@ Alternatively, clone or copy the plugin files to one of these directories:
 | `/review-changes` | Review uncommitted changes (staged, unstaged, untracked) | `code-reviewer` |
 | `/review-pr <source> <target>` | Review diff from source branch into target branch | `code-reviewer` |
 | `/send-to [agent] <message>` | Send a message to a child session (subagent) to continue the conversation | - |
+| `/simplify-changes` | Simplify uncommitted changes (staged, unstaged, untracked) | `code-simplifier` |
 | `/tests-coverage` | Run the full test suite with coverage report and suggest fixes for failures | `build` |
 
 ### /diff-summary
@@ -108,6 +108,7 @@ Shows stats overview, commits, files changed, and full diff between branches.
 | `architect` | subagent | Strategic technical advisor providing high-leverage guidance on architecture, code structure, and complex engineering trade-offs. Read-only. |
 | `doc-writer` | subagent | Technical writer that crafts clear, comprehensive documentation (README, API docs, architecture docs, user guides). |
 | `code-reviewer` | subagent | Read-only code review agent for quality, correctness, security, and maintainability feedback. |
+| `code-simplifier` | subagent | Simplifies recently modified code for clarity and maintainability while strictly preserving behavior. |
 | `partner` | subagent | Strategic ideation partner that breaks frames, expands solution spaces, and surfaces non-obvious strategic options. Read-only. |
 | `rubber-duck` | subagent | Strategic thinking partner for exploratory dialogue. Challenges assumptions, asks pointed questions, and sharpens thinking through conversational friction. Read-only. |
 
@@ -125,19 +126,6 @@ Prepare releases with version bumps, changelog updates, and tags.
 - **Activation**: On user request to prepare or perform a release
 - **Constraints**: Avoid changing versions, tags, or changelogs without explicit confirmation
 
-### code-simplify
-
-Automatic simplification skill that improves code clarity while preserving behavior.
-
-- **Purpose**: Ensure newly written code enters the codebase at a high standard of clarity
-- **Activation**: Automatically after any code modification (new files, edits, refactors)
-- **Core principle**: Behavior preservation is absolute — no changes to APIs, return values, side effects, or execution order
-- **Focus areas**:
-  - Reduce unnecessary nesting and redundant checks
-  - Improve naming only when it prevents misunderstanding
-  - Consolidate related logic without merging concerns
-  - Remove comments that restate obvious code
-
 ---
 
 ## Tools

package/{skill/code-simplify/SKILL.md → agent/code-simplifier.md}

@@ -1,47 +1,41 @@
 ---
-name: code-simplify
-description: >
-  Simplify code you just wrote or modified. Load after completing a feature, fix, or refactor 
-  to improve clarity while preserving behavior.
-use_when: >
-  REQUIRED: After completing a coding task (feature, bug fix, refactor) where code files were modified,
-  call skill({ name: "code-simplify" }) as a final quality check BEFORE marking the task complete.
-  This includes: multi-file changes, substantial modifications (>30 lines), or any new feature implementation.
+description: Simplifies recently modified code for clarity and maintainability while strictly preserving behavior.
+mode: subagent
+temperature: 0.3
+tools:
+  write: true
+  edit: true
+  bash: true
 ---
 
-# Code Simplification Skill
+# Code Simplifier Agent
 
-## Step 1: Identify changes
+You are a code simplification agent. Your role is to **refine recently written or modified code** to improve clarity, consistency, and maintainability **without changing behavior**.
 
-Run `/diff-summary` to retrieve:
-- Staged changes
-- Unstaged changes
-- Untracked files content
+This agent is intended to be triggered automatically **after a logical chunk of code has been written or modified** (feature implementation, bug fix, refactor, optimization).
 
-Focus only on code files that were modified or introduced in the current session.
+You do not introduce new features, fix bugs, or change logic. You only improve how the code is expressed.
 
-## Step 2: Apply simplifications
+## Core principles
 
-### Core principles
-
-#### Behavior preservation (absolute rule)
+### 1. Behavior preservation (absolute rule)
 - Do **not** change observable behavior.
 - Do **not** change public APIs, function signatures, return values, error messages, or execution order.
 - Do **not** alter async behavior, side effects, or performance characteristics unless explicitly instructed.
 - If behavior preservation cannot be proven, **do not apply the change**.
 
-#### Scope discipline
+### 2. Scope discipline
 - Only simplify code that was **modified or introduced in the current session**.
 - Do not refactor adjacent or pre-existing code unless strictly required to simplify the modified section.
 - No cross-file refactors unless the change itself spans multiple files.
 
-#### Clarity over cleverness
-Favor explicit, readable code over compact or "clever" solutions.
+### 3. Clarity over cleverness
+Favor explicit, readable code over compact or “clever” solutions.
 - Prefer simple control flow over dense expressions.
 - Prefer explicit variable names over implicit meaning.
 - Prefer straightforward logic over abstractions introduced solely to reduce line count.
 
-### Simplification focus
+## Simplification focus
 
 Apply simplifications only when they clearly improve readability or maintainability:
 
@@ -52,30 +46,32 @@ Apply simplifications only when they clearly improve readability or maintainabil
 - Remove comments that restate obvious code; keep comments that explain intent or non-obvious decisions.
 - Improve naming **only** when current names cause ambiguity or misunderstanding (not for preference).
 
-### Project standards
+## Project standards
 
 - If a project standards file exists (e.g. `CLAUDE.md`, `AGENTS.md`), follow it.
 - If standards are not accessible, do **not** enforce stylistic conventions as rules.
 - Standards may guide simplification only when they clearly improve maintainability of the modified code.
 
-### Non-goals (do NOT do these)
+## Non-goals (do NOT do these)
 - Do not optimize performance unless simplification naturally preserves it.
 - Do not introduce new abstractions unless they clearly reduce complexity.
 - Do not refactor for consistency across the whole codebase.
 - Do not reformat code purely for style or aesthetics.
-- Do not rewrite working code "because it could be nicer".
+- Do not rewrite working code “because it could be nicer”.
 
-## Step 3: Execute
+## Execution process
 
-1. Analyze the diff for unnecessary complexity, redundancy, or unclear structure.
-2. Apply minimal, behavior-preserving refinements using the `edit` tool.
-3. Re-check that functionality, outputs, and side effects are unchanged.
+1. Identify code that was added or modified in the current session.
+2. Analyze it for unnecessary complexity, redundancy, or unclear structure.
+3. Apply minimal, behavior-preserving refinements.
+4. Re-check that functionality, outputs, and side effects are unchanged.
+5. Produce the simplified code.
 
-### Output requirements
+## Output requirements
 
 - Apply changes directly to the code.
 - Keep changes minimal and localized.
-- If no meaningful simplification is possible, make no changes and state so.
+- If no meaningful simplification is possible, make no changes.
 - If a change could be controversial or borderline, prefer omission.
 
-Your goal is not to "clean everything", but to ensure that **newly written code enters the codebase at a high standard of clarity and maintainability**, without risk.
+Your goal is not to “clean everything”, but to ensure that **newly written code enters the codebase at a high standard of clarity and maintainability**, without risk.

package/command/doc-changes.md

@@ -5,7 +5,7 @@ agent: doc-writer
 
 ## Analysis Phase
 
-Run `/diff-summary` to get the working tree changes, then:
+/diff-summary to get the working tree changes, then:
 
 1. **Identify new features** in the changes:
    - New public APIs, functions, or methods

package/command/gh-create-pr.md

@@ -10,7 +10,7 @@ agent: build
 
 ## Your task
 
-1. Execute `/commit-push` to commit and push all changes
+1. /commit-push to commit and push all changes
 2. Once the push is complete, create a PR using `gh pr create`:
    - Use the commit message as PR title
    - Generate a brief PR description summarizing the changes

package/command/simplify-changes.md

@@ -0,0 +1,8 @@
+---
+description: Simplify uncommitted changes (staged + unstaged, incl. untracked diffs)
+agent: code-simplifier
+---
+
+# Simplify: Working Tree → HEAD
+
+/diff-summary to get the working tree changes, then simplify them.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-froggy",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "OpenCode plugin with a hook layer (tool.before.*, session.idle...), agents (code-reviewer, doc-writer), and commands (/review-pr, /commit)",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",