decision-tracker

Track git file changes, session context, and decision history.

5|Updated Oct 14, 2025
One-click install
npx skills add https://github.com/Shakes-tzd/contextune --skill decision-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-tracker
Source: https://github.com/Shakes-tzd/contextune/tree/main/skills/decision-tracker
Command: npx skills add https://github.com/Shakes-tzd/contextune --skill decision-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps Claude informed about the project's evolution by recording in-session changes, uncommitted work, and historical decisions using git as the single source of truth. This avoids stale mental models and duplicates.

Core Features & Use Cases

  • In-session state checks: surface git diff, git status, current branch, and uncommitted changes.
  • Between-session context: capture commits, file changes, and historical decisions for later querying.
  • Historical decisions: store and query past research findings and architectural decisions.
  • Pre-emptive state awareness: auto-activates before duplicating work or starting new tasks to prevent rework.

Quick Start

Enable auto-activation by enabling this skill and then query questions like "What changed since the last session?" or "Show me current state" to retrieve up-to-date state and history. You can also run "what happened in the previous session" for retrospective reasoning.

Frequently Asked Questions about decision-tracker

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

FAQPage Schema
How do I track file changes and decisions across multiple development sessions?

Git-powered state tracking captures file changes, uncommitted work, and architectural decisions using git as the single source of truth. Enable the Skill to auto-activate before tasks, then query "What changed since the last session?" to retrieve up-to-date diffs, commits, and decision history across in-session and between-session contexts.

Can I query git diff and session history to avoid duplicating work?

Yes. The Skill surfaces git diff, git status, current branch, and uncommitted changes automatically. Pre-emptive state awareness activates before starting new tasks, retrieving past research findings and architectural decisions so you can reference prior reasoning without rework.

What's the best way to maintain context about my project's evolution during development?

Record in-session changes and uncommitted work using git-backed state tracking. The Skill stores queryable decision history and delivers real-time state sync, differential context generation, and historical decision loading, keeping Claude informed and preventing stale mental models.

How do I retrieve what happened in previous sessions without manual notes?

Query "What happened in the previous session?" to activate retrospective decision loading. The Skill auto-activates on state queries, delivering git-powered awareness of file changes, session context, and historical decisions across between-session and historical contexts.

Does this work with uncommitted changes and branch tracking?

Yes. The Skill enforces automated git hooks and token budgeting while integrating git status checks and decision-query utilities. It captures uncommitted work, current branch state, and file changes to prevent duplicated reasoning and surface real-time in-session state sync.

What are the limitations of git-based state tracking for decision history?

State tracking depends on git availability and assumes changes are committed or tracked as uncommitted diffs. Decision queries retrieve only what has been recorded in git history; manually deleted commits or untracked changes outside git cannot be recovered.