drift-status

Report Git commits, diff statistics, and changed files since session start.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Hamad-Center/drift-skills --skill drift-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift-status
Source: https://github.com/Hamad-Center/drift-skills/tree/main/claude-code/drift-status
Command: npx skills add https://github.com/Hamad-Center/drift-skills --skill drift-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a quick, read-only overview of code changes made since a Git session began, helping you stay aware of scope creep and track progress against your ticket.

Core Features & Use Cases

  • Session Tracking: Monitors Git commits and diffs relative to a starting point.
  • Change Visualization: Displays commit history, diff statistics, and changed file lists.
  • Uncommitted Changes: Checks for any uncommitted modifications.
  • Recent History: Shows a summary of recent Drift sessions for context.
  • Use Case: After a coding session, you can quickly run /drift-status to see exactly what you've changed, ensuring you're on track with your Jira ticket's requirements.

Quick Start

Run /drift-status to see the changes made since your current drift session started.

Frequently Asked Questions about drift-status

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

FAQPage Schema
How do I check my git diff and commit history during a coding session?

To check your git diff and commit history, you can run a read-only status command that displays commits, changed files, and diff statistics relative to a starting SHA without altering the repository state.

What is the best way to monitor code changes and prevent scope creep against a Jira ticket?

Monitoring code changes to prevent scope creep involves comparing your current commits and uncommitted modifications against a session's start SHA, providing a summary of file changes and diff statistics to track progress.

Does this git status tracking method modify my repository or commit changes?

No, this git status tracking method is strictly read-only. It reports on uncommitted modifications and recent session history without executing any write operations or altering your repository state.

Can I see uncommitted changes and recent session history without running git log manually?

Yes, you can see uncommitted changes and recent session history without running git log manually by executing a single command that aggregates commit tracking data and recent session context.

How do I track code evolution from a specific start SHA to my current working directory?

Tracking code evolution from a specific start SHA requires a read-only session monitoring process that calculates diff statistics and lists changed files between that initial commit hash and your current working state.