사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/asta-nguyen/agent-devkit --skill lean-audit시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Lean Audit
Overview
Run a read-only whole-repo simplicity audit. Report validated cuts; do not edit, delete, commit, open a PR, or post comments.
When to use
Use for audits of over-engineering, bloat, or simplification. Do not use for diff-only review, correctness, security, performance, generic test coverage, or style; route those concerns to review or debugging.
Process
- Establish root. Read applicable instructions and inspect
git statuswithout
changing it. Record root, exclusions (.git, generated output, vendored code, node_modules, and build caches), and every inspected first-party area. If the user explicitly includes an excluded path, state that override. If a required area or repository-wide search is unavailable, report Audit incomplete: <specific limitation> and do not make a lean verdict.
- Inventory source, structure, entrypoints, manifests, dependencies,
configuration, commands, and tests. Use rg and direct reads. Before judging a candidate, use FFF multi-pattern grep (fallback: rg) to search callers, registrations, and dynamic-reference variants, then inspect relevant configuration, tests, and extension requirements.
- Report only validated cuts with one of these tags:
delete, stdlib, native, yagni, or shrink. Omit ambiguous candidates. Preserve explicit requirements, repository conventions, compatibility boundaries, required validation, and behavior-protecting tests. Route out-of-scope concerns to review/debugging.
- Rank the largest credible cut first. Report savings only when supported;
never imply that a change was applied.
Output
# Lean audit
Scope: <repository root>; exclusions: <paths>; inspected: <first-party areas>
1. delete: <path:line> <cut>. <replacement>. evidence: <paths/searches>
net: -<N> lines, -<M> dependencies possible.Every finding needs an exact repository-relative path:line, evidence, and a replacement. For shrink, show the shorter equivalent form. After complete coverage with no validated cut, keep the header and scope, then output Lean already. Ship. and omit findings and net. If coverage is incomplete, output the limitation instead.
Quick reference
| Tag | Meaning |
|---|---|
delete | Remove code or a dependency with no required use. |
stdlib | Replace custom behavior with a standard-library API. |
native | Replace custom machinery with a platform-native feature. |
yagni | Remove speculative or unused abstraction. |
shrink | Keep behavior while making code materially smaller. |
Example
src/format.js:18 — stdlib: replace the hand-written extension parser with node:path.extname; evidence: callers and tests cover the same input boundary.
Common mistakes
- Calling a style preference bloat without behavior or reuse evidence.
- Calling code dead after checking only one direct occurrence.
- Removing a factory or validation despite an explicit extension contract.
