Record git commit SHA and branch with ticket info in `.drift/config.json`.
npx skills add https://github.com/Hamad-Center/drift-skills --skill drift-start
Please help me install this Agent Skill. Skill: drift-start Source: https://github.com/Hamad-Center/drift-skills/tree/main/claude-code/drift-start Command: npx skills add https://github.com/Hamad-Center/drift-skills --skill drift-start
This Skill prevents scope creep and forgotten requirements by automatically tracking code changes against your Jira ticket's acceptance criteria.
CONTEXT.md for continuity across work sessions.Use the drift-start skill to begin tracking work on ticket PROJ-123.
High-intent search queries and answers about installing and using this skill.
To track code changes against Jira tickets, you can initiate a session that records your current git commit SHA and branch alongside ticket details. This monitors code modifications against acceptance criteria to flag unrequested features.
Git commit tracking with Jira integration works by saving your session state in a local config file and optionally fetching ticket summaries and descriptions directly from Jira to define your planned work scope.
The best way to start monitoring scope creep is to begin a tracking session by providing your ticket ID, which automatically captures your current git branch and commit state to establish a baseline for planned work.
Yes, you can use this to compare code against Jira acceptance criteria. It optionally fetches ticket details from Jira and uses the recorded git state to flag unrequested features or forgotten requirements.
The tracking session does persist context across work periods by saving session history to a CONTEXT.md file. This ensures continuity and prevents lost requirements when you resume work on a ticket.
You do not need to manually configure git ignore before tracking code changes. The session automatically creates a .drift directory for configuration and ensures it is ignored by git upon initialization.
venturecraneUpdates the active session context with git branch, commit, and optional metadata.
Hamad-CenterAnalyze code changes against Jira acceptance criteria and update CONTEXT.md.
flurdyCompare GitHub PR changes and CI status against linked Jira ticket requirements.
LukasStricklerGenerate Conventional Commits messages from repository history and local configuration.