Index of every page on this site: llms.txt
All skills
google avatar

/egm-drift-report

@70406c4
by googlegoogle/elephant-goldfish-model22k stars
1,589
Run it yourself

Runs drift detection on all design documents to check for document and code consistency. Produces an actionable report with differences. Use when the user asks to detect drift or check for consistency across all design documents or READMEs in a directory.

Use this Skill: https://skilld.dev/gh/google/elephant-goldfish-model/egm-drift-report

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈68 tokens for metadata: the name and description. ≈702 when used: this file. ≈416 more on demand in 3 files.

How this Skill uses context

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

This Skill turns off automatic use in Claude Code. Its description stays out of the automatic Skill list by default.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

  2. List Documents: List all files in the design directory.

  3. 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."
  4. 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:

      ## <DESIGN_DOC_NAME>
      
      <Bulleted list of specific divergences found>
      <Or "No drift detected">
  5. 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    This skill provides a utility for identifying 'drift' or discrepancies between design documents and their corresponding code implementations. It operates by reading local files, performing code searches, and generating a local markdown report. The security profile is consistent with standard development tools.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 70406c4. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 4 weeks ago
disable-model-invocation
true

README badge

README badge for google/elephant-goldfish-model/egm-drift-report