사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/legout/skills --skill review-codebase-architecture시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Adapted from `mattpocock/skills` at commit 3cca18b368ae95cdbdebbff572ccafa662551015 (MIT).Architecture review
Review architecture without editing code or defining final interfaces. Use the repository's domain terms and existing ADRs. Use this vocabulary consistently: module, interface, implementation, depth, deep, shallow, seam, adapter, leverage, and locality.
Scope
Use the user's named area. Otherwise inspect recent history for repeatedly changed hotspots before scanning broadly. Follow actual call paths and tests.
Look for evidence of:
- shallow modules whose interface nearly matches their implementation;
- one concept scattered across many files;
- duplicated orchestration around a missing deep interface;
- tests that reach through internals because no stable public seam exists;
- details leaking between coupled modules; and
- extracted helpers that improve unit-test access but reduce locality.
Apply the deletion test: deleting a good deep module should expose and concentrate meaningful complexity, not merely move its name.
Report
Rank only evidence-backed candidates. For each include files, observations, current interface, hidden complexity, proposed deeper module or seam, benefits, risks, affected ADRs, blast radius, and one strength: Strong, Worth exploring, or Speculative.
Use Markdown by default. When the user asks for a visual report or diagrams materially clarify the relationships, follow the HTML report guide and write the result outside the repository unless the user asks otherwise.
End with one recommendation and a justified do-nothing option.
Boundary
Do not edit code or settle interfaces. Ask which candidate to explore, then route the selected candidate to shape-design. Use write-implementation-plan only after the design is approved.
