New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Drift Check

by joshukraine in joshukraine/dotfiles

Pre-PR advisory check for deviations from the project spec. An agent skill from joshukraine/dotfiles.

MITAuto-check passedDevelopment

Install Drift Check

skills CLI
$ npx skills add joshukraine/dotfiles --skill drift-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install joshukraine/dotfiles drift-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/joshukraine/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/.claude/skills/drift-check .claude/skills/drift-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
drift-check
GitHub stars
429
Token cost
~1.2k tokens
SKILL.md length
580 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

Pre-PR advisory check for deviations from the project spec. An agent skill from joshukraine/dotfiles.

  • Works in 5 steps: Identify scope → Identify the relevant spec → Scan for deviation signals → …
  • Development work in your project
  • SKILL.md covers Your task and Important
  • Calls git

What it does

Drift Check is an agent skill from joshukraine/dotfiles. Pre-PR advisory check for deviations from the project spec. Read-only analysis.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Git. The repository describes itself as: :roundpushpin: My dotfiles for macOS using Neovim, Zsh, and Ghostty + Tmux. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/drift-check”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify scope
  2. Identify the relevant spec
  3. Scan for deviation signals
  4. Check documentation gaps
  5. Report findings

What it can do on your machine

Read from SKILL.md and the folder at commit b59ad5b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Drift Check loads about 1.2k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 580 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from joshukraine/dotfiles at commit b59ad5b, republished under its MIT licence (© joshukraine). 580 words, ~1,161 tokens.

Download SKILL.mdSave it as .claude/skills/drift-check/SKILL.md (or your agent's skills folder).
name
drift-check
description
Pre-PR advisory check for deviations from the project spec. Read-only analysis.

Drift Check

Pre-PR deviation check against the project spec. Run this before /create-pr to verify alignment between implementation and documentation.

Reference: See ~/.claude/docs/prd-workflow/spec-driven-development.md §2–§4 for the deviation threshold, workflow, and checkpoint cadence that this skill operationalizes.

Not the same as /code-review — that inspects the diff for correctness bugs and cleanups; this checks the diff against the spec and docs for deviations. They run at the same pre-PR moment and complement each other.

Your task

Perform a lightweight, advisory review of the current branch's changes against the project's spec and living documents. This is a read-only check — do not modify any files.

Step 1: Identify scope
  • Determine the default branch first — don't assume main. Run git rev-parse --abbrev-ref origin/HEAD; it prints e.g. origin/main or origin/master, and the part after origin/ is the base branch for the commands below. If it errors (no origin/HEAD set locally), fall back to git remote show origin (read its "HEAD branch:" line) or default to main. Use this detected base wherever <base> appears below. (Run the detection as a plain command and substitute the result literally — don't wrap it in $(...), which triggers a permission prompt.)
  • Run git log <base>..HEAD --oneline to see all commits on this branch
  • Run git diff <base>...HEAD --stat to see all files changed
  • Determine which feature area this work relates to (from branch name, commit messages, or changed files)
Step 2: Identify the relevant spec
  • Check for docs/prd/ROADMAP.md — if it exists, identify which phase or item this work relates to
  • Check for docs/prd/ files that cover the feature area
  • Check for living documents (domain model, integration guides, runbooks) that describe the current state of the affected models or features
  • If no spec exists for this work (e.g., a bug fix or chore with no PRD entry), note that and skip to Step 4
Show full SKILL.md (279 more words)Show less
Step 3: Scan for deviation signals

Review git diff <base>...HEAD (the base branch detected in Step 1) for changes that cross the deviation threshold:

Flag if present:

  • New or removed database migrations (new models, columns, associations)
  • Changes to model validations or lifecycle (status enums, state transitions)
  • New or changed URL patterns (routes file changes)
  • Changes to authorization rules (policy files)
  • New or altered mailer actions or notification triggers
  • API contract changes (new endpoints, changed request/response shapes)

For each flagged change, check whether the relevant spec or living document already describes it. If it does, no action needed. If it doesn't, this is a potential deviation.

Step 4: Check documentation gaps
  • If docs/prd/CHANGELOG.md exists, check whether any deviations found in Step 3 have already been logged
  • If docs/prd/ROADMAP.md exists and this work corresponds to a checkbox item, check whether the checkbox is marked [x]
  • Check whether the branch's linked issue (from branch name gh-<N>) has closing keywords in any commit or is ready to be referenced in a PR description
Step 5: Report findings

Present a concise report with these sections:

text
## Drift Check — [branch name]

### Spec Reference
[Which PRD section or living document this work relates to, or "No spec found"]

### Deviation Signals
[List any changes that cross the threshold but aren't in the spec]
[Or: "No deviations detected"]

### Documentation Status
- CHANGELOG: [entry exists / entry needed / not applicable]
- ROADMAP: [checkbox marked / checkbox not marked / not applicable]
- Issue linking: [ready / needs attention]

### Recommended Actions
[Bulleted list of any actions needed before creating the PR]
[Or: "Clear to proceed with /create-pr"]

Important

  • This is advisory, not blocking. The developer decides what needs action.
  • Do not modify any files — no CHANGELOG entries, no ROADMAP updates, no code changes.
  • Do not re-read files you've already seen in this session unless needed for the deviation check.
  • Keep it fast. Target: under 30 seconds for a typical PR. Don't exhaustively read every PRD file — focus on the one or two that are relevant.
  • If no PRD exists for the project, check against living documents (domain model, README, CLAUDE.md architectural guardrails). The deviation threshold still applies — it just measures against whatever the authoritative reference is.

© joshukraine, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in claude/.claude/skills/drift-check of joshukraine/dotfiles.

Open the folder on GitHubat commit b59ad5b

Compare with similar skills

Drift Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Drift Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Drift Check this skilljoshukraine/dotfiles429—~1.2kAutomated safety check: PassMIT
MoAI SPEC Workflowmodu-ai/moai-adk1.2k—~5.1kAutomated safety check: PassApache-2.0
Reviewdevoxx/DevoxxGenieIDEAPlugin684—~652Automated safety check: PassMIT
Pi En Progressiveshare-skills/pi108—~9.3kAutomated safety check: WarnApache-2.0
Ad ReviewCorridorTech/PoseCap224—~2.4kAutomated safety check: NotesApache-2.0
Pi Enshare-skills/pi108—~18kAutomated safety check: WarnApache-2.0

Similar skills

  • MoAI SPEC Workflow

    modu-ai/moai-adk

    Manages SPEC documents for MoAI-ADK development, with GEARS or EARS requirement notation, acceptance criteria and a link into the Plan-Run-Sync workflow.

    1.2k GitHub stars~5.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Review

    devoxx/DevoxxGenieIDEAPlugin

    Review local code changes for bugs, regressions, missing tests, and pragmatic improvements.

    684 GitHub stars~652 tokensUpdated 11 days ago
    DevelopmentAuto-check passed

  • Pi En Progressive

    share-skills/pi

    PI Cognitive AI. An agent skill from share-skills/pi.

    108 GitHub stars~9.3k tokensUpdated 3 mo ago
    DevelopmentAuto-check: warnings

  • Ad Review

    CorridorTech/PoseCap

    Two-axis fresh-context code review per WORKFLOW §10. An agent skill from CorridorTech/PoseCap.

    224 GitHub stars~2.4k tokensUpdated 3 days ago
    DevelopmentAuto-check: notes

  • Pi En

    share-skills/pi

    PI Cognitive AI. An agent skill from share-skills/pi.

    108 GitHub stars~18k tokensUpdated 3 mo ago
    DevelopmentAuto-check: warnings

  • Release Management

    ruby-git/ruby-git

    Prepares and publishes new releases of the ruby-git gem including version bumps, changelog updates, tagging, and gem publishing.

    1.8k GitHub stars~3.1k tokensUpdated 8 days ago
    DevelopmentAuto-check passed

More from joshukraine/dotfiles

All 24 skills in this repo

  • Todoist CLI

    joshukraine/dotfiles

    Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI.

    429 GitHub starsUsed in 1 repo~6.9k tokens
    Auto-check passed

  • Autopilot Triage

    joshukraine/dotfiles

    Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.

    429 GitHub stars~2.1k tokensUpdated 3 days ago
    Auto-check passed

  • Checkpoint

    joshukraine/dotfiles

    Quick 2-minute status update on current phase, completed work, blockers, and health check.

    429 GitHub stars~600 tokensUpdated 3 days ago
    Auto-check passed

  • Create PR

    joshukraine/dotfiles

    Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.

    429 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

  • Debrief

    joshukraine/dotfiles

    Detailed technical walkthrough covering architecture, test coverage, product tour, and key design decisions.

    429 GitHub stars~2.5k tokensUpdated 3 days ago
    Auto-check passed

  • Dustoff

    joshukraine/dotfiles

    Assess a project that's been dormant for months and produce a prioritized re-entry plan — lifecycle stage, what's stale or broken, and how far the project's tooling has drifted from current…

    429 GitHub stars~3.1k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Drift Check

What does Drift Check do?

Pre-PR advisory check for deviations from the project spec. An agent skill from joshukraine/dotfiles. Drift Check is an agent skill from joshukraine/dotfiles. Pre-PR advisory check for deviations from the project spec.

When should I use Drift Check?

Drift Check fits situations like: development work in your project.

How do I install Drift Check in Claude Code?

Run `npx skills add joshukraine/dotfiles --skill drift-check -a claude-code`. Or copy the skill folder (claude/.claude/skills/drift-check in joshukraine/dotfiles) into .claude/skills/drift-check in your project. Claude Code loads it when a task matches its description.

How do I install Drift Check in Codex?

Run `npx skills add joshukraine/dotfiles --skill drift-check -a codex`. Or copy the skill folder (claude/.claude/skills/drift-check in joshukraine/dotfiles) into .agents/skills/drift-check in your project. Codex loads it when a task matches its description.

Can I use Drift Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add joshukraine/dotfiles --skill drift-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/drift-check, .gemini/skills/drift-check, .github/skills/drift-check and .opencode/skills/drift-check in your project.

What does Drift Check need to run?

Going by SKILL.md and its folder, Drift Check needs the command-line tools its instructions call (git).

Does Drift Check access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Drift Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Drift Check use?

Drift Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Drift Check use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Drift Check?

Skills that share tags, products or a category with Drift Check: MoAI SPEC Workflow (modu-ai/moai-adk, 1.2k stars), Review (devoxx/DevoxxGenieIDEAPlugin, 684 stars), Pi En Progressive (share-skills/pi, 108 stars) and Ad Review (CorridorTech/PoseCap, 224 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Drift Check?

joshukraine (a GitHub user) maintains it in joshukraine/dotfiles, which has 429 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 6, 2026.

Source: joshukraine/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.