google/elephant-goldfish-model

egm-drift-report

Runs drift detection on all design documents to check for document and code consistency.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/google/elephant-goldfish-model --skill egm-drift-report

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Detect Drift In Designs and Code

When running in Codex or ChatGPT Work, first read Codex integration. In Claude Code or Cowork, read ${CLAUDE_PLUGIN_ROOT}/docs/claude.md first.

When the user asks to detect drift across all designs or a set of READMEs, the goal is to identify all instances where the codebase has diverged or failed to implement the specifications described by those designs or READMEs.

  1. Check Input: Verify a directory containing design documents or READMEs

is provided. If not provided, ask the user to specify the target directory.

  1. List Documents: List all files in the design directory.
  2. Analyze: For EACH design document:
  • Contextualize: Read the design document. Identify the intent,

proposed changes, and specific filenames/symbols mentioned.

  • Locate Source: Find the corresponding source code files in the

source tree. If paths aren't explicit, use code search or grep to locate the relevant classes, functions, or API endpoints mentioned in the doc. Prompt the user to add missing links to the document to make future detection cheaper.

  • Verify: Read the current state of those source files.
  • Detect Drift: Compare the design vs. reality. Look specifically for:
  • Missing Features: Logic described in the doc but absent in the code.
  • Incomplete Models: Dataclasses/Classes/Structs/Protos missing fields

specified in the design.

  • Logic Shortcuts: Hardcoded values where dynamic logic was planned.
  • Architectural Divergence: Implementation using different

patterns/libraries than proposed.

  • Filter: Report ONLY the differences. Do not describe what is working

or what matches. If the code matches the design perfectly, output "No drift detected."

  1. Report: Produce a single report listing all discrepancies found.
  • Append the analysis for each file to {YYYY-MM-DD}_DRIFT_REPORT.md

using your file-writing tool.

  • Strict Format:
markdown
        ## <DESIGN_DOC_NAME>

        <Bulleted list of specific divergences found>
        <Or "No drift detected">
  1. Guidance
  • Be rigorous. If a design doc mentions a specific object, field or file

name and the code doesn't have it, that is a reportable drift. Double check for coverage. If there is some part of the logic that is not referenced in a design or README, this is a reportable drift.

  • Read files liberally to ensure you are looking at the current state

of the code, not relying on memory.

  • Process the files sequentially to ensure the tool output buffer doesn't

overflow.

같은 저장소의 Skills

더 많은 Skills

모든 Skills