check-drift

Compare code against fingerprint.json and map changes to JIRA stories.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hariinfo/agentic-code-template --skill check-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-drift
Source: https://github.com/hariinfo/agentic-code-template/tree/main/.claude/skills/drift-detector
Command: npx skills add https://github.com/hariinfo/agentic-code-template --skill check-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift detection helps identify when code changes diverge from a known fingerprint baseline, surfacing mismatches in files, signatures, and structure that could impact modernization stories.

Core Features & Use Cases

  • Detect drift by comparing current code against modernization-output fingerprint.json.
  • Map changed files to JIRA stories to surface affected work and guide prioritization.
  • Generate a structured drift report with the highest-impact changes (CRITICAL/SIGNIFICANT/MINOR/NEW SCOPE) for quick remediation.

Quick Start

Run the drift detector to compare the current repository against the fingerprint baseline and generate a drift report.

Frequently Asked Questions about check-drift

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

FAQPage Schema
How do I detect code drift against a baseline fingerprint?

To detect code drift, compare current repository file hashes and content changes against a fingerprint.json baseline. This process surfaces file additions, deletions, and modifications to identify structural mismatches.

How does code drift detection map changes to JIRA stories?

Code drift detection maps changed files to JIRA stories by analyzing modernization-output jira-stories.md alongside the fingerprint baseline. This mapping surfaces affected work and guides remediation prioritization.

What is the best way to classify the impact of code drift?

The best way to classify code drift impact is to generate a structured drift report. This report categorizes the highest-impact changes into CRITICAL, SIGNIFICANT, MINOR, or NEW SCOPE for quick remediation.

Do I need specific files to run a code drift analysis?

You need access to modernization-output/{slug}/fingerprint.json and modernization-output/{slug}/jira-stories.md files. These baseline files provide the necessary file hashes and story mappings for drift analysis.

When should I run a codebase drift detection analysis?

You should run drift detection after analysis snapshots are generated. This timing ensures you accurately surface any current file additions, deletions, and modifications that have diverged from the known baseline.

Can I use git diff to assess code drift impact for modernization?

While git diff shows raw changes, drift detection analyzes file hashes and key signatures against a baseline to classify impact severity. It then maps these structural mismatches to JIRA stories for modernization assessment.