메뉴
Cleans up code at a chosen intensity/latitude over a scope (diff/area/repo) - simplify, de-cruft. Loads a stack reference. Use when tidying, not reviewing or strictness upgrades (develop-maintain).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Creates a new self-contained subagent identity in .claude/agents/ and its .github/agents/ (Copilot) and .junie/agents/ (Junie) mirrors. Use when introducing a new expert identity to the klank agent system.
Checks klank's agent setup for consistency - mirror parity, frontmatter, cross-refs, stale paths, descriptions. Use before any commit under .claude/, .github/agents/, or docs/agents/.
Diagnoses a failing CI/CD run via failed-step logs, debug logging, re-runs, flaky triage, and local repro. Loads a platform reference (e.g. github-actions). Use when a pipeline run is failing.
Audits and hardens an existing CI/CD pipeline against supply-chain and injection attacks. Loads a platform reference (e.g. github-actions) with a full checklist. Use when securing pipelines.
Keeps CI/CD pipelines healthy via dependency and runner-image updates, pruning, and reusable-pipeline versioning. Loads a platform reference (e.g. github-actions). Use for routine upkeep.
Scaffolds a secure-by-default CI/CD pipeline - least-privilege, pinned deps, caching, matrices, reusable parts. Loads a platform reference (e.g. github-actions). Use when creating a pipeline.
| name | develop-clean |
| description | Cleans up code at a chosen intensity/latitude over a scope (diff/area/repo) - simplify, de-cruft. Loads a stack reference. Use when tidying, not reviewing or strictness upgrades (develop-maintain). |
| argument-hint | <scope: diff|area|repo> <intensity: light|standard|exhaustive> <latitude: none|safe|free> |
Improve existing code's quality without changing what it does (unless explicitly allowed), at a dial-able effort and risk. This is the active application of dev-principles (least code) to code that already exists - cut the bloat, keep the guardrail.
Use to tidy or refactor existing code. To find what to fix see develop-review; for version/strictness upgrades see develop-maintain; for new code see develop-write.
Confirm all three before starting; if unspecified, default to diff / standard / safe and say so.
diff (the current PR/change), area (a module or directory), or repo (the whole codebase). Larger scope is worked in reviewable batches, not one diff.light - obvious quick wins only: dead code, unused imports/vars, formatting the formatter missed, trivial renames.standard - plus de-duplicate, simplify expressions and control flow, tighten types locally (behavior-preserving narrowing; project-wide strict-flag migration is develop-maintain), small local extractions, swap a hand-rolled bit for a stdlib or existing helper.exhaustive - every smell: naming, cohesion, comments, error handling, micro-redundancy; examine each line. Slow and thorough.none - in place only; no signature, public API, or file-structure changes. Smallest diff, lowest risk.safe - behavior-preserving refactors: extract/inline/move within existing boundaries, rename internals; public API unchanged.free - anything, including API, structure, or dependency changes, provided the tests prove behavior is preserved.qa-test) or drop to light/none.references/typescript.md for the stack's concrete cleanups.free, an intentional API change updates its tests and is called out, not hidden.none/safe is a bug, not a cleanup; a behavior fix is develop-write/develop-review work - surface it, do not smuggle it in.repo/exhaustive.light/none.develop-write / develop-maintain.