- Home
- Skills
- Shakes Tzd
- Contextune
- Decision Tracker
decision-tracker_skill
- HTML
4
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill shakes-tzd/contextune --skill decision-tracker- SKILL.md16.1 KB
Overview
This skill provides git-powered state awareness for conversational development sessions. It tracks in-session changes, between-session diffs, and historical decisions so the assistant avoids stale context and duplicated work. The system auto-activates for state queries and before potentially conflicting file operations.
How this skill works
It inspects git status, diffs, and logs to build a lightweight differential summary at session start and on demand. A PreToolUse hook checks file state before edits and a SessionStart hook injects changes since the last session. Decisions, research, and plans are stored in a compact decisions.yaml and queried selectively to load only relevant context.
When to use it
- When asking “what changed since last session?” or “show me what happened”.
- Before editing or writing files to avoid conflicts with external changes.
- Before starting research, planning, or making a decision to reuse prior work.
- After the user reports external commits or edits.
- When you want a concise differential summary instead of reloading entire project context.
Best practices
- Rely on the PreToolUse hook rather than manually running git commands before edits.
- Always query decisions.yaml for research, plans, or decisions before starting new work.
- Treat research entries as expirable (e.g., 6 months) and re-run only when expired.
- Use the manual session-status script for a full snapshot when needed.
- Load only the relevant entries from decisions.yaml to minimize token usage.
Example use cases
- User asks “what files did we work on?” → run session-status and summarize commits and changed files.
- Attempting to Edit a file after external change → PreToolUse warns and suggests re-reading the file.
- Starting research on a topic → query decisions.yaml and reuse existing findings if available.
- Beginning a planning session → check for active plans to continue existing work instead of recreating.
- After a user commits changes outside the assistant → run session-status and report the differential.
FAQ
It injects only new information: in-session checks ~200–500 tokens, between-session diffs ~1–2K tokens, and selected decision loads ~2–5K tokens, keeping total well under a full reload.
What triggers the skill automatically?
State queries, PreToolUse before file operations, and explicit session start or manual status checks trigger the skill.