跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

omh-ai-slop-cleaner

[omh] Hermes AI slop cleaner workflow: delete AI-generated slop, dead code, and duplication while observable behavior stays identical. Use when the user says: ai-slop-cleaner, cleanup, deslop, refactor, risky, behavior-preserving refactor, risk analysis, refactor workflow.

rlaope · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add rlaope/oh-my-hermes --skill omh-ai-slop-cleaner

技能说明


name: "omh-ai-slop-cleaner" description: "[omh] Hermes AI slop cleaner workflow: delete AI-generated slop, dead code, and duplication while observable behavior stays identical. Use when the user says: ai-slop-cleaner, cleanup, deslop, refactor, risky, behavior-preserving refactor, risk analysis, refactor workflow." metadata: hermes: tags: [workflow, oh-my-hermes, maintenance] category: maintenance phase: cleanup role: handoff-guide quality_tier: regression-gated

Ai Slop Cleaner

This is a Hermes-native ai-slop-cleaner workflow skill.

Why This Exists

ai-slop-cleaner exists to keep maintenance work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.

Do Not Use When

  • The goal is new or changed behavior rather than removing existing code; a plain refactor, feature, or fix request belongs to ultrawork.
  • The cleanup would change architecture or module boundaries and needs its execution shaped into phases first; use refactor-plan, or ralplan when the direction itself is still contested.
  • The user wants existing code judged rather than changed; use code-review for a bug-first review and failure-signal-audit for swallowed failures.

Examples

Good example:

  • Prompt: $ai-slop-cleaner remove duplicated router branches and lock behavior with regression tests before refactoring.
  • Expected behavior: Plan cleanup, preserve behavior, delete or simplify code, and prove it with targeted tests.
  • Why: The request is maintenance cleanup with regression risk.

Bad example:

  • Prompt: ai-slop-cleaner: treat casual chat or unaccepted work as if this workflow already produced verified results.
  • Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing ai-slop-cleaner.
  • Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.

Completion Checklist

  • The selected coding or runtime owner is named before any implementation claim.
  • Prepared handoff, dispatch, execution, verification, review, CI, and merge states are separated.
  • The final status cites observed runtime evidence or keeps the work prepared_not_observed.
  • When Hermes is the selected coding owner, use hermes_coding_harness/v1 to keep builder, verifier, reviewer, docs, and PR lanes separate.
  • Report the current harness stage, owner, next action, and missing evidence without claiming PR creation, review, CI, merge-readiness, or merge until matching runtime observations exist.

Recovery Notes

  • If the selected executor is unavailable, ask for Codex, Claude Code, Hermes, or another runtime before retrying.
  • If dispatch or result evidence is missing, keep the handoff prepared_not_observed and expose the next observable action.

Workflow Lane

  • Current lane: Coding handoff (idea-to-deploy, llm-app-dev, cto-loop, deploy-and-monitor, code-review, build-failure-triage, verification-gate, security-safety-review, +13 more) - coding owners, handoffs, review, CI, and merge evidence.
  • If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.

Use When

Use when the goal is removing existing low-quality, duplicated, or AI-generated code and the observable behavior must not change; lock behavior with tests before and after the edits.

Strong routing signals: `ai-slop-cleaner`, `$ai-slop-cleaner`, `cleanup`, `deslop`, `refactor`, `risky`, `behavior-preserving refactor`, `risk analysis`, `refactor workflow`, `legacy refactor`, `리팩터링`, `리팩토링`, `위험 분석`, `변경 범위 제한`, `회귀 테스트`

Catalog Metadata

Category: maintenance Phase: cleanup Hermes role: handoff-guide Quality tier: regression-gated Reasoning demand: heavy

Quality bar:

  • Lock current behavior with regression checks before non-trivial cleanup.
  • Classify before deleting: every finding names one category from the slop taxonomy - duplication, dead code, needless abstraction, boundary violation, missing tests, or templated defaults - so the pass order below can own it.
  • Run single-smell passes in fixed order, re-verifying between passes and never bundling categories: dead-code deletion, then duplicate removal, then naming and error handling, then test reinforcement; the full contract is omh-ai-slop-cleaner/references/cleanup-passes.md.
  • When the user names no target smell, run detection first and hand back the inventory: prepared linter and dead-code commands are named per stack in the reference and stay prepared_not_observed until run.
  • Prefer deletion, reuse, and boundary repair over new abstractions.
  • Rerun verification after cleanup before claiming behavior is preserved, and close with the four-part report: changed files, simplifications, behavior lock, remaining risks.

Handoff policy:

Use Hermes to define cleanup scope and regression checks; route behavior-preserving edits to the selected coding runtime once tests are clear.

Executor readiness:

  • When accepted work mutates code, check executor_readiness/v1 for the selected Codex, Claude Code, Hermes, or oh-my runtime path before first dispatch.
  • If readiness is missing or blocked, ask the user to choose another coding agent, configure PATH, continue in Hermes, or keep a prompt/runtime handoff; retry only after that state changes.
  • A readiness probe is not dispatch, implementation, verification, review, CI, merge-readiness, or merge evidence.

Delegation transparency:

  • When delegating, show the composed delegate prompt in a fenced code block in the status message; truncate a long prompt to a bounded preview ending with ... [truncated, N chars total] — the user must see WHAT was asked, not just that something was.
  • Name every delegated or parallel lane's model and, when the host exposes it, its reasoning effort inline as (model effort)
阅读完整来源 ↗