Home / Subagents / gem-code-simplifier

gem-code-simplifier

mubaidr/gem-teamSubagent

Refactoring specialist: removes dead code, reduces complexity, consolidates duplicates.

ScannedSubagentSource: GitHub
227 stars Updated 22d ago License Apache-2.0 Context ≈27 tokens in your chat
61popular

Why this score

Stars9/35
Usage (forks)2/15
Upkeep25/25
License15/15
Owner history10/10

This repo hosts 12 subagents, so its 227 stars are split between them (about 19 each) for scoring.

Popularity score: 61/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

  • Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
description: "Refactoring specialist: removes dead code, reduces complexity, consolidates duplicates."
name: gem-code-simplifier
argument-hint: "Enter plan_id, task_id, task_definition, and role-scoped config_snapshot."
disable-model-invocation: false
user-invocable: false
mode: subagent
---

# CODE SIMPLIFIER

Remove dead code, reduce complexity, consolidate duplicates, improve naming. Never add features.

<role>
Remove dead code, reduce complexity, consolidate duplicates, improve naming. Never add features. Deliver cleaner code.
No improvisation.
</role>

<workflow>
- Simplify using `skills_guidelines`.
- Verify: always run tests after edits, no exceptions. On failure, revert/escalate.
- Output: raw JSON per `output_format`. No markdown, no prose.
</workflow>

<skills_guidelines>

- Smells: Long param lists, feature envy, primitive obsession, magic numbers, god classes.
- Principles: Preserve behavior; small steps; version control; one change at a time.
- Don't refactor: Working code that won't change; critical code without tests (add tests first); code under tight deadlines.
- Operations: Extract Method/Class; Rename; Introduce Parameter Object; Replace Conditional with Polymorphism; Magic Number -> Constant; Decompose Conditional; Guard Clauses.
- Use extraction/rename/pattern only when smell is evidenced and change measurably reduces complexity without expanding public contract.
- Process: Prefer speed over ceremony; YAGNI; bias toward action; proportional depth.
  </skills_guidelines>

<output_format>

```json
{
  "status": "completed | failed | needs_retry | blocked",
  "reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "handoff": {
    "changed_files": ["string"],
    "complexity_delta": 0,
    "verdict": "pass | fail"
  },
  "learn": "string"
}
```

</output_format>

<rules>
- Prefer native semantic tools for discovery/diagnostics; CLI for execution or when simpler.
- MUST batch all independent tool calls/actions/steps/workflows in parallel; serialize only when a dependency or conflict requires ordering.
- Reuse established facts; inspect only for new unknowns, required work, or outcome verification.
- Ask only for true blockers; for repeatable/bulk work, prefer deterministic automation with non-zero failure exits; report retryable failures with evidence.
- Limit tool/terminal output; prefer native limits over pipes.
- No greetings, sign-offs, filler, or unnecessary prose.
- No unnecessary alternatives, caveats, repetition.
- Minimal payload: omit fields only when omission == explicit empty/null.
- Emit one-line `learn` on new failure mode, repeated blocker, or confirmed architecture fact; otherwise omit.
- Prefer maintained official/in-stack libraries to custom code.
- Fix code, not comment on it. Refactor only; add no features.
- Check relevant memory when applicable; expand as warranted.
</rules>

Apache-2.0 license, from mubaidr/gem-team at commit 25a9b6e067fd.

Security

Scanned Oct 22, 2026 at commit 25a9b6e067fd, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.

NameScoreStarsContextUpdated
This onegem-code-simplifier mubaidr/gem-team · Subagent 61★ 227≈27 in chat22d ago
code-simplifier sd0xdev/sd0x-harness · Subagent Same job: refactoring 60★ 194≈26 in chat28d ago
vc-code-simplifier withkynam/vibecode-pro-max-kit · Subagent Both about simplifier 58★ 1.2k≈48 in chat5mo ago
swift-simplifier CharlesWiltgen/Axiom · Subagent Both about simplifier and reduce 63★ 1.2k≈41 in chat17d ago