Analyze code changes against Jira acceptance criteria and update CONTEXT.md.
npx skills add https://github.com/Hamad-Center/drift-skills --skill drift-sync
Please help me install this Agent Skill. Skill: drift-sync Source: https://github.com/Hamad-Center/drift-skills/tree/main/claude-code/drift-sync Command: npx skills add https://github.com/Hamad-Center/drift-skills --skill drift-sync
This Skill automates in-depth code analysis, identifies scope creep by comparing against Jira ticket acceptance criteria, and maintains project context.
CONTEXT.md with session summaries, preserving critical decisions and analysis across work sessions.Run the drift-sync skill to perform a deep analysis of all code changes since your last drift session started.
High-intent search queries and answers about installing and using this skill.
Detect scope creep by analyzing git diffs against Jira acceptance criteria to flag unrequested features. This process gathers git data, evaluates file contents, and structures findings into technical decisions, architectural impact, and identified drift from the original plan.
Code review context persistence saves session summaries by updating a CONTEXT.md file. It works by capturing deep analysis of git diffs and preserving critical technical decisions and architectural evaluations across multiple work sessions.
Sync code review summaries to Jira by optionally fetching ticket details and posting session summaries as comments. This maintains alignment with project requirements by linking deep code analysis directly to the relevant Jira tickets.
Yes, you can analyze all code changes since a session began by leveraging the full context window. This comprehensive code review gathers git data and evaluates file contents to provide detailed insights into technical decisions and architectural impact.
Jira integration requires no special dependencies to analyze file contents and git diffs. It optionally fetches ticket details and posts session summaries as comments, comparing implemented code against explicit Jira acceptance criteria to flag scope drift.
The best way to maintain project context is performing multi-step deep code analysis that structures findings into architectural impact and next steps. It updates CONTEXT.md with session summaries, preserving critical decisions across work sessions.
davidarceGenerate conventional git commits with JIRA ticket enrichment from diffs.
quaid-appDraft structured architectural proposals with problem statements, decisions, and risks.
Rune-kitCompare git changes against a task plan to classify scope creep.
datamonsterrCompare FR-* and SC-* requirements against code to produce drift reports.