skills.rest
JeromyJSmith
JeromyJSmithCOMMUNITY
Explore all skills by this author →
GitHub

source-command-gf-drift-check

Compare current Graphify code graphs against saved snapshots to detect drift.

3|Updated May 11, 2026
Search Tags:#refactoring#drift detection#dependency analysis#code graph#graphify#snapshot comparison
One-click install
npx skills add https://github.com/JeromyJSmith/lattice-platform --skill source-command-gf-drift-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-gf-drift-check
Source: https://github.com/JeromyJSmith/lattice-platform/tree/main/.agents/skills/source-command-gf-drift-check
Command: npx skills add https://github.com/JeromyJSmith/lattice-platform --skill source-command-gf-drift-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly identify when the current code graph has changed in unexpected ways since your last Graphify snapshot, preventing hidden coupling and dead-code regressions.

Core Features & Use Cases

  • Snapshot drift detection: Compares the current code graph against the last saved Graphify snapshot to surface differences.
  • Post-commit validation: Use it after large commits to detect unintended architecture changes.
  • Dead code and coupling discovery: Flags potential dead code introductions and unexpected dependencies created by refactors.

Quick Start

Run the migrated source command gf-drift-check to compare the latest code graph with your previous Graphify snapshot.

Frequently Asked Questions about source-command-gf-drift-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect unexpected code graph drift after a large refactor?▼

Code graph drift detection compares your current Graphify-derived code graph against a saved snapshot to surface unexpected coupling, missing edges, or newly introduced dead code following large commits or architecture changes.

What is the best way to check for hidden coupling and dead code regressions post-commit?▼

Post-commit validation via snapshot drift detection compares the latest code graph with your previous Graphify baseline, flagging potential dead code introductions and unexpected dependencies created by refactors.

How does snapshot comparison work for dependency analysis in refactoring?▼

Snapshot comparison applies deterministic validation by evaluating the current code graph against the most recent saved Graphify snapshot, reporting drift deltas to clearly identify missing edges or new coupling.

When do I need to run a code graph drift check?▼

You need to run a code graph drift check after large commits, refactors, or architecture changes to prevent hidden coupling and dead-code regressions from going unnoticed in your codebase.

Do I need a previous Graphify snapshot to detect code graph drift?▼

Yes, detecting code graph drift requires a previously saved Graphify snapshot to serve as a deterministic baseline for comparing the current code graph and reporting structural drift deltas.

Can code graph drift detection flag newly introduced dead code?▼

Yes, code graph drift detection flags potential dead code introductions and unexpected dependencies by comparing the current code graph structure against the stored baseline snapshot.

Related Skills

Explore More Software Engineering Skills→
pko89403pko89403
1

graphify-manager

Automate end-to-end Graphify refresh from staged corpus to graph outputs.

Community
Advanced
sambeausambeau
5

codebase-memory-quality

Identify dead code and high-cost functions using graph-based queries.

Community
Advanced
nathanvalenathanvale
2

index-graph-navigator

Query a codebase call graph for blast radius and dead code analysis.

Community
Intermediate
ByronWilliamsCPAByronWilliamsCPA

codebase-memory

Trace code dependencies and call chains using a pre-built knowledge graph.

Official
Intermediate