drift-check

Analyze branch commits for deviations from project specifications and living documents.

421|49|Updated Jul 3, 2014
One-click install
npx skills add https://github.com/joshukraine/dotfiles --skill drift-check-joshukraine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift-check
Source: https://github.com/joshukraine/dotfiles/tree/main/claude/.claude/skills/drift-check
Command: npx skills add https://github.com/joshukraine/dotfiles --skill drift-check-joshukraine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that Pull Requests (PRs) do not contain deviations from the project's specifications and living documents, providing a pre-PR advisory check.

Core Features & Use Cases

  • Pre-PR Deviation Check: Analyzes changes against project specifications and living documents.
  • Read-only Analysis: No modifications to files are made.
  • Feature Area Identification: Determines the relevant feature area based on branch names, commit messages, or changed files.
  • Spec Scanning: Identifies and flags deviations in database migrations, model validations, URL patterns, authorization rules, mailer actions, and API contracts.
  • Documentation Gap Check: Assesses CHANGELOG and ROADMAP entries and issue linking.
  • Report Generation: Provides a concise report with deviation signals, documentation status, and recommended actions.

Quick Start

Run the drift-check skill to verify PR alignment with the project spec and living documents.

Frequently Asked Questions about drift-check

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

FAQPage Schema
How do I check if my code changes deviate from the project spec before creating a PR?

Pre-PR deviation checks analyze branch commits against project specifications and living documents to flag misalignments in database, model, URL, authorization, mailer, and API changes. This read-only process generates a report with deviation signals and recommended actions.

What is spec compliance analysis for pull requests?

Spec compliance analysis scans branch commits to verify code changes align with project specifications and living documents. It identifies the relevant feature area and checks for deviations in database migrations, model validations, URL patterns, authorization rules, mailer actions, and API contracts.

How do I detect missing documentation updates like CHANGELOG and ROADMAP entries before submitting a PR?

Documentation gap checks assess CHANGELOG and ROADMAP entries alongside issue linking by scanning branch commits. This read-only analysis produces a concise report detailing documentation status and recommended actions to ensure spec alignment.

Can I run a spec compliance check without modifying my codebase?

Read-only spec compliance analysis operates on a branch's commits without making any file modifications. It performs a pre-PR advisory check, generating a concise report with deviation signals and documentation status to ensure project alignment.

Does PR deviation detection work with database migrations and API contract changes?

PR deviation detection scans database migrations and API contract changes against project specifications. It also covers model validations, URL patterns, authorization rules, and mailer actions, operating read-only on branch commits to flag any spec misalignments.

What are the limitations of automated pre-PR spec compliance checks?

Automated pre-PR spec compliance checks provide advisory reports only and do not modify code. They rely on branch names, commit messages, and changed files to identify feature areas, meaning poorly named branches or commits may affect feature area detection accuracy.