check-updates

Detect upstream repository changes and assess impacts on documentation and demos.

4|1|Updated Feb 22, 2026

Search Tags:#git #documentation #version control #impact assessment #agent analysis #submodule management

Ready to run

npx skills add https://github.com/7hinkDifferent/agent-cracker --skill check-updates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-updates
Source: https://github.com/7hinkDifferent/agent-cracker/tree/main/.claude/skills/check-updates
Command: npx skills add https://github.com/7hinkDifferent/agent-cracker --skill check-updates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintain the integrity of analyzed AI agent projects by detecting upstream repository changes and assessing their potential impact on documentation and demos.

Core Features & Use Cases

Upstream Change Detection: Automatically checks if the code of analyzed AI agents has been updated in their original repositories.
Impact Assessment: Analyzes which documentation sections and interactive demos might be affected by these upstream changes.
Commit Stamping: Allows users to mark the current state of a submodule as analyzed, updating tracking information.
Use Case: After a period of inactivity, run this Skill to quickly see if any of the AI agents you've documented have new commits, and understand which parts of your analysis might need revisiting.

Quick Start

Run the check-updates skill to see if any agents have changed since the last analysis.

Frequently Asked Questions about check-updates

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

FAQPage Schema

How do I detect upstream repository changes in AI agent submodules?▼

Detect upstream repository changes by comparing your local commit with the remote HEAD. This process identifies new updates in agent repositories and classifies file changes by their potential impact on your analysis dimensions.

What is the best way to assess the impact of git changes on documentation?▼

Assess the impact of git changes by cross-referencing modified files with your documentation sections. This evaluates which specific documentation parts and interactive demos are affected by the latest upstream repository commits.

Can I stamp a current git commit as analyzed in agents.yaml?▼

Yes, you can stamp the current commit as analyzed. This updates the tracking metadata in agents.yaml and relevant documentation files to record the exact repository state you have reviewed.

How do I check if interactive demos are affected by version control updates?▼

Check interactive demos for update impacts by cross-referencing changed files with demo source references. This identifies exactly which interactive demos require revisiting after version control changes occur.

Do I need to manually compare local commits with remote HEAD for impact assessment?▼

No, manual comparison is unnecessary. The skill automatically compares your current local commit with the remote HEAD of specified agent repositories to deliver a structured impact assessment.

When should I run an upstream change detection check on my agent repositories?▼

Run an upstream change detection check after a period of inactivity. This quickly reveals if documented AI agents have new commits and highlights which parts of your analysis need revisiting.