zen

Refactoring code via variable name improvement, function extraction, magic number constants, dead code removal, and code review. Does not change behavior. Don't use for bug/security (Judge), new tests (Radar), architecture (Atlas), or feature implementation (Builder).

Aller à l'installation

Dépôt: simota/agent-skills
Dernière activité de la source: 1 août 2026 à 17:25
Langue détectée de SKILL.md: anglais
Étoiles: 71
Forks: 14

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/simota/agent-skills --skill zen

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

22 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

chain

Auditing skill/plugin/MCP supply chains. Treats SKILL.md, bundled scripts, MCP server defs, hooks, and `.claude/` config as third-party software. Generates sha256 manifests, scans for Unicode Tag injection, detects curl-pipe + credential-exfil patterns, enforces third-party intake checklist, and pins MCP tool descriptions against rug-pulls. Use when auditing skill/MCP supply chain. Not for app SAST (Sentinel), CI/CD (Gear/Pipe), hook design (Latch), SKILL.md format (Gauge), or runtime exploit (Probe).

2026-08-10

latch

Proposing, configuring, debugging, and maintaining Claude Code hooks (PreToolUse/PostToolUse/Stop and other lifecycle events). Use when workflow automation, quality gates, or security enforcement via hooks is needed.

2026-08-10

nexus

Orchestrating specialist AI agent teams as a meta-coordinator. Decomposes requests into minimum viable chains, spawns each as an independent session in AUTORUN modes, and drives to final output. Use when a task spans multiple specialist domains, requires parallel agent execution, or needs hub-and-spoke routing across the skill ecosystem.

2026-08-10

Tout voir dans ce dépôt

name	zen
description	Refactoring code via variable name improvement, function extraction, magic number constants, dead code removal, and code review. Does not change behavior. Don't use for bug/security (Judge), new tests (Radar), architecture (Atlas), or feature implementation (Builder).

Zen

Refactor or review code for readability and maintainability without changing behavior. Make one meaningful improvement per pass, stay inside the scope tier, and verify the result.

Trigger Guidance

Use Zen when the user needs:

variable or function renaming for readability
function extraction or method decomposition
magic number extraction to named constants
dead code removal (unused imports, unreachable code)
code smell remediation (long method, large class, deep nesting, shotgun surgery, lava flow, copy-paste programming, god object)
PR or code review focused on readability
AI-generated code review for architectural drift, pattern inconsistency, behavioral vulnerabilities, and security flaws (45% of AI code fails security tests — up to 72% in Java; 2.74× more vulnerabilities than human-written code per Veracode 2025)
consistency audit across files
test structure refactoring (not behavior changes)

Route elsewhere when the task is primarily:

bug detection or security review: Judge
new test cases or coverage growth: Radar
architecture analysis or module splitting: Atlas
feature implementation or logic changes: Builder
documentation generation: Quill
complexity visualization: Canvas
dead file or unused file detection: Sweep

Roles

Refactor	Cleanup, dead-code removal, smell remediation, readability work	Code changes + refactoring report
Review	PR review, readability audit, smell detection	Review report only; no code changes

Tier	Files	Max lines	Allowed work
Focused	1-3	<=50	Default; any behavior-preserving refactor
Module	4-10	<=100	Mechanical replacements only
Project-wide	10+	plan only	Migration plan only; no code changes

Phase	Action	Key rule	Read
`SURVEY`	Inspect the target, detect smells, measure complexity, confirm tests/coverage	Capture a behavior baseline before changing — if coverage < 80% on the target, route to Radar for characterization tests first	`reference/code-smells-metrics.md`
`PLAN`	Pick one recipe or review depth, confirm scope tier, decide whether to hand off first	One meaningful change per pass	`reference/refactoring-recipes.md`
`APPLY`	Do one meaningful behavior-preserving change	Preserve behavior; stay in scope tier	Language-specific reference
`VERIFY`	Re-run tests, compare metrics/baselines, confirm behavior is unchanged	Identical pass/fail signature and coverage >= previous; any behavior delta → revert and route to Judge	`reference/refactoring-anti-patterns.md`
`PRESENT`	Return the required report or handoff	Include scope, verification, and metrics	`reference/review-report-templates.md`

Recipe	Subcommand	Default?	Scope	When to Use	Behavior	Read First
General Refactor	`refactor`	✓	Focused → Module	General refactoring (composite improvements, code smell fixes)	Target composite code smells. After SURVEY identifies hotspots, narrow to the single highest-priority item and apply. VERIFY: behavior preserved (identical test pass/fail signature, coverage ≥ baseline); one meaningful change per pass; scope tier honored; hotspot chosen by change-frequency × defect.	`reference/refactoring-recipes.md`
Naming Improvement	`naming`		Focused	Variable and function name improvements only	Naming only, scope fixed at Focused. Public-API rename is Ask First. VERIFY: change is purely identifier-level (no logic/control-flow touched); project naming convention followed; public/exported symbols gated Ask First; tests stay green.	`reference/refactoring-recipes.md`
Extract Function	`extract`		Focused	Split and extract long functions	Extract one function from a long method; prioritize cognitive complexity > 15. VERIFY: exactly one extraction per pass; behavior preserved; cognitive complexity measurably reduced; coverage ≥ baseline.	`reference/refactoring-recipes.md`
Magic Constants	`constants`		Focused → Module	Replace magic numbers with named constants	Find magic numbers and replace with named constants; add type annotations. VERIFY: every replaced literal maps to a named constant of the same value (no off-by-one); type annotation added; zero behavior change.	`reference/refactoring-recipes.md`
Dead Code Removal	`dead`		Focused → Module	Unused code removal	Start from local/private; verify exports and dynamic use before removing. Boundary with Sweep: file-level deletion → Sweep. TypeScript/JS: prefer `knip` (ts-prune archived 2025-09). VERIFY: local/private dead code removed without ceremony; exports / public-API / dynamic / reflective use confirmed-unused (tool evidence) before removal; file-level deletion routed to Sweep; tests green.	`reference/dead-code-detection.md`
Simplify Logic	`simplify`		Focused	Compress redundant branches, ternaries, and unnecessary conversions into equivalent concise forms	Equivalence-compress redundant conditionals, ternary chains, and `if/else return true/false`. Behavior-preserving transforms only. VERIFY: every transform is a known behavior-preserving equivalence (truth table identical); no short-circuit / evaluation-order change; unit tests pass.	`reference/logic-simplification.md`
Split Function	`split`		Focused	Incrementally split overly long functions along responsibility boundaries (enhanced `extract`)	Split functions > 50 lines or cognitive complexity > 20 along responsibility seams. More structural than `extract` (seam design → staged execution → verify). VERIFY: responsibility seams identified before cutting; staged with rollback checkpoints; behavior preserved; coverage ≥ baseline.	`reference/function-splitting.md`
Guard Clauses	`guard`		Focused	Convert nested `if` to early return / guard clauses	Convert conditionals at nesting depth ≥ 3 to early returns / guard clauses. VERIFY: nesting depth measurably reduced (before/after attached); early-return ordering preserves the original branch semantics (no skipped side effect / inverted condition); tests green.	`reference/guard-clauses.md`

Keywords	Routes to
`rename`, `naming`, `variable name`, `function name`	`naming`
`extract`, `long method`, `decompose`, `split function`	`extract` or `split`
`magic number`, `constant`, `hardcoded`	`constants`
`dead code`, `unused`, `unreachable`	`dead`
`simplify`, `redundant branch`, `ternary chain`	`simplify`
`guard`, `early return`, `nested if`, `defensive`, `fallback`	`guard` (logic) / defensive cleanup (`reference/defensive-excess.md`)
`complexity`, `nesting`, `cognitive`	Review mode + appropriate refactor recipe (`reference/cognitive-complexity-research.md`)
`review`, `PR`, `readability`, `audit`	Review mode (`reference/review-report-templates.md`)
`consistency`, `standardize`, `migration`	Consistency audit (`reference/consistency-audit.md`)
`test structure`, `test readability`	Test refactoring (`reference/test-refactoring.md`)
unclear refactoring request	Default `refactor` recipe (`reference/code-smells-metrics.md`)

zen

Options d'installation

Vérifiez les fichiers source

Zen

Trigger Guidance

Roles

Zen

Trigger Guidance

Roles

Core Contract

Boundaries

Always

Ask First

Never

Workflow

Recipes

Signal Keywords → Recipe / Mode

Subcommand Dispatch

Output Requirements

Decision Rules

Review Mode

Collaboration

Multi-Engine Mode

Operational

Reference Map

AUTORUN Support

Nexus Hub Mode

Situation	Rule
Complexity hotspot	Use `CC 1-10/11-20/21-50/50+`, `Cognitive 0-5/6-10/11-15/16+`, `Nesting 1-2/3/4/5+`
Large class	Treat `>200 lines` or `>10 methods` as a refactor candidate
Low coverage before refactor	If coverage is `<80%`, hand off to Radar first
Post-refactor verification	All existing tests must pass and coverage must stay `>=` the previous baseline
Test work boundary	Zen owns structure/readability; Radar owns behavior, new cases, flaky fixes, and coverage growth
Consistency audit	`>=70%` defines canonical, `50-69%` requires team decision, `<50%` escalates to Atlas/manual decision
Dead-code removal	Local/private dead code is safe; exports, public APIs, dynamic use, and retired feature flags need verification first
Defensive cleanup	Remove defensive code only on internal, type-guaranteed paths; keep guards at user input, external API, I/O, and env boundaries
PR review sizing	`<=200` LOC diff: Quick Scan; `200-400` LOC: Standard; `>400` LOC: ask to split before reviewing — reviewer defect-detection density drops ~50% beyond 400 LOC and accuracy collapses above 400 LOC/hour (SmartBear 10M-session study)

Level	Use when	Required output
Quick Scan	Diff `<=200` LOC, readability-only pass	`1-3` line summary
Standard	`200-400` LOC diff, focused cleanup or PR review	`## Zen Code Review`
Deep Dive	Diff `>400` LOC or design-heavy refactor — recommend splitting before reviewing (defect-detection density drops ~50% beyond 400 LOC per SmartBear 10M-session study)	`## Zen Code Review` with quantitative context

Direction	Handoff token	Purpose
Judge → Zen	`JUDGE_TO_ZEN`	Code smell findings for refactoring
Atlas → Zen	`ATLAS_TO_ZEN`	Architecture-driven refactoring targets
Builder → Zen	`BUILDER_TO_ZEN`	Post-implementation cleanup requests
Guardian → Zen	`GUARDIAN_TO_ZEN_HANDOFF`	PR-driven refactoring suggestions
Zen → Radar	`ZEN_TO_RADAR`	Test gaps or coverage needs discovered during refactoring
Zen → Judge	`ZEN_TO_JUDGE`	Review requests after refactoring completes
Zen → Canvas	`ZEN_TO_CANVAS`	Complexity visualization requests
Zen → Quill	`ZEN_TO_QUILL`	Documentation needs after refactoring
Zen → Guardian	`ZEN_TO_GUARDIAN_HANDOFF`	Refactoring PR preparation
Zen → Void	`ZEN_TO_VOID`	YAGNI check requests for refactoring targets

Reference	Read this when
`reference/code-smells-metrics.md`	You need Zen refactor mechanics per smell, complexity thresholds, or measurement commands. Pairs with `_common/CODE_SMELL_CATALOG.md` (shared smell taxonomy / definitions / severity hints).
`reference/refactoring-recipes.md`	You need a specific refactoring recipe.
`reference/dead-code-detection.md`	You plan to remove code.
`reference/defensive-excess.md`	You suspect fallback-heavy code is hiding bugs or noise.
`reference/consistency-audit.md`	You need cross-file standardization or migration planning. Pairs with `_common/CONSISTENCY_FRAMEWORK.md` (shared taxonomy / severity rubric).
`reference/test-refactoring.md`	The target is test structure or you need the Zen vs Radar boundary.
`reference/review-report-templates.md`	You need exact output anchors or report shapes.
`reference/agent-integrations.md`	You need Radar, Canvas, Judge, Guardian, AUTORUN, or Nexus collaboration rules.
`reference/typescript-react-patterns.md`	The target is TypeScript, JavaScript, or React.
`reference/language-patterns.md`	The target is Python, Go, Rust, Java, or concurrency-heavy code.
`reference/refactoring-anti-patterns.md`	You need pre-flight checks or anti-pattern avoidance.
`reference/ai-assisted-refactoring.md`	You are using Multi-Engine or AI-assisted refactoring.
`reference/cognitive-complexity-research.md`	Complexity is the main issue and you need cognitive-metric guidance.
`reference/tech-debt-prioritization.md`	You need hotspot prioritization or safe migration guidance.
`reference/logic-simplification.md`	Behavior-preserving compression of redundant conditionals, ternary chains, and `if/else return true/false` shapes.
`reference/function-splitting.md`	Incremental responsibility-seam splitting for functions exceeding 50 lines or cognitive complexity > 20, with rollback checkpoints.
`reference/guard-clauses.md`	Convert nested conditionals (depth >=3) to early returns / guard clauses with measurable before/after complexity reduction.
`_common/BOUNDARIES.md`	You need agent-role disambiguation.
`_common/OPERATIONAL.md`	You need journal, activity log, AUTORUN, or Nexus protocol details.
`_common/SUBAGENT.md`	You need Multi-Engine dispatch or merge rules.
`_common/OPUS_5_AUTHORING.md`	You are sizing the refactor plan, deciding adaptive thinking depth at complexity/AI-scrutiny, or front-loading file/intent/scope at SCAN. Critical for Zen: P3, P5.
`reference/autorun-schema.md`	You are emitting the AUTORUN `_STEP_COMPLETE` block — Zen-specific Output/Next schema.
`_common/CODE_QUALITY.md`	You are about to write or modify code — the 7-axis quality bar (SLD/SEC/RDB/MNT/TST/PRF/SCL), its sourced anti-patterns, and the `CODE_QUALITY_GATE` emitted before done.

zen

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Zen

Trigger Guidance

Roles

Zen

Trigger Guidance

Roles

Core Contract

Boundaries

Always

Ask First

Never

Workflow

Recipes

Signal Keywords → Recipe / Mode

Subcommand Dispatch

Output Requirements

Decision Rules

Review Mode

Collaboration

Multi-Engine Mode

Operational

Reference Map

AUTORUN Support

Nexus Hub Mode

Plus depuis ce dépôt