stale-changes-check

stale-changes-check is a skill for Claude Code from Jerry0022/dotclaude. It costs 28 tokens per session (393 once invoked), scanned A, original, MIT.

An automatic session-start check for Git repositories. Git is a tool that tracks code changes and can send commits to shared remote repositories.

In plain words
What is it for?
Checking the current repository, and optionally other configured repositories, whenever a coding-agent session starts.
Why use it?
It warns you about uncommitted changes, commits that have not been pushed, or saved stashes that could otherwise be forgotten.

Skill for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Part of the devops plugin — 18 skills, 12 agents, 9 hooks, 1 MCP server shipped together

Good fit Checking the current repository, and optionally other configured repositories, whenever a coding-agent session starts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jerry0022/dotclaude/stale-changes-check
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Jerry0022/dotclaude --skill stale-changes-check
Clone the repo
git clone --depth 1 https://github.com/Jerry0022/dotclaude

Made for: Claude Code.

Or install devops, the plugin that ships this one along with the rest of its 18 skills, 12 agents, 9 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for stale-changes-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/jerry0022/dotclaude/stale-changes-check/github.svg)](https://agentmods.dev/skills/jerry0022/dotclaude/stale-changes-check)
Your own site
<a href="https://agentmods.dev/skills/jerry0022/dotclaude/stale-changes-check"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/stale-changes-check/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for stale-changes-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/jerry0022/dotclaude/stale-changes-check"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/stale-changes-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 393 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00393
Opus 5.5 $0.00011 $0.00157
Sonnet 5.5 $0.00006 $0.00079
Haiku 4.5 $0.00003 $0.00039

Measured 2mo ago against content hash 511e94cce6ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

stale-changes-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/devops/scheduled-tasks/stale-changes-check/SKILL.md · 46 lines

What it actually says

Stale Changes Check

Runs automatically at every session start via hooks/session-start/ss.git.check.js. Silent when everything is clean. Only surfaces a brief warning when issues are found.

What the hook checks

  1. git status --porcelain — uncommitted changes
  2. git log --branches --not --remotes --oneline — unpushed commits
  3. git stash list — stash entries

Always checks the current working directory. Optionally checks additional repos defined in ~/.claude/scheduled-tasks/stale-changes-check/reference.md:

## Repos to monitor
- ~/IdeaProjects/my-app
- ~/IdeaProjects/my-other-app

Output behaviour

  • Clean → hook exits silently, nothing shown to user.
  • Issues found → hook writes a structured summary to stdout; Claude relays a brief inline warning to the user (no full report, no table).

Findings are never coupled to a question. The hook always emits them and instructs the assistant to restate them in its final message, before any completion card. When a workspace issue is also present, the AskUserQuestion block is layered on top — so an interactive session asks, while a scheduled, cron or headless session (which cannot answer a modal) still reports what was found instead of dropping it with the skipped question. See hooks/lib/git-check-output.js.

Constraints

  • Read-only — hook never makes any git changes
  • No cron registration — this is a direct SessionStart hook, not a scheduled task
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 46 lines · 28 tokens per session scan A 511e94cce6ec

Subscribe to this mod's changes

stale-changes-check is a skill published in the GitHub repository Jerry0022/dotclaude (6 stars, last pushed 11d ago), licensed MIT. It adds 28 tokens to every session and 393 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

stale-changes-check compared with skills from other repositories

stale-changes-check next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
stale-changes-checkJerry0022/dotclaudeSkill611d agoMITA28Claude Code
merge-batchdiegosouzapw/OmniRouteSkill83k6d agoMITA46Claude Code
prowler-commitprowler-cloud/prowlerSkill15kyesterdayApache-2.0A44Claude Code, Codex
gh-auth-isolationgithub/gh-awSkill5.6kyesterdayMITA20Claude Code, Codex
github-skillzeenie-ai/OpenCompanySkill1.1kyesterdayMITA51Claude Code
comet-githubrpamis/cometSkill3.3kyesterdayMITA72Claude Code, Codex
release-helperSahir619/fable-methodSkill2.3k1mo agoMITA43Claude Code