repo-wiki-detect
Detect code changes since last wiki update using git diff. Identifies added, modified, deleted, and renamed files to determine which documentation pages need updates.
Detect code changes since last wiki update using git diff. Identifies added, modified, deleted, and renamed files to determine which documentation pages need updates.
Repo Wiki Detect Changes Skill
Detect code changes and determine documentation impact.
Purpose
This skill analyzes what changed in the codebase since the last wiki update:
- Files added, modified, deleted, or renamed
- Components affected by changes
- Documentation pages that need updates
- Citations that may have shifted
When to Use
Use this skill:
- After making code changes
- Before running
repo-wiki-update - To see what documentation will be affected
Step-by-Step Instructions
Step 1: Load Last Baseline Commit
LAST_COMMIT=$(uv run python -c "import json; print(json.load(open('.repo_wiki/state.json'))['last_run_commit'])")
CURRENT_COMMIT=$(git rev-parse HEAD)
Step 2: Compute Git Diff
git diff --name-status "$LAST_COMMIT".."$CURRENT_COMMIT" > .repo_wiki/changes.diff
Step 3: Parse Changes
Categorize into added, modified, deleted, renamed files.
Step 4: Map Files to Components
Determine which components are affected by changes.
Step 5: Identify Impacted Pages
Match changed files to existing documentation pages.
Step 6: Detect New/Deleted Modules
Check for components that need new pages or archiving.
Output Files
.repo_wiki/change_set.json- Structured change data.repo_wiki/logs/detection.log- Summary report
Success Criteria
- ✅ Change set created
- ✅ Impacted pages identified
- ✅ New modules detected
- ✅ Deleted modules identified
Next Steps
After detection:
- Update documentation: Read
repo-wiki-update/SKILL.md
You Might Also Like
Related Skills
update-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
vercel
docstring
Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
pytorch
docs-writer
Always use this skill when the task involves writing, reviewing, or editing files in the `/docs` directory or any `.md` files in the repository.
google-gemini
write-concept
Write or review JavaScript concept documentation pages for the 33 JavaScript Concepts project, following strict structure and quality guidelines
leonardomsoresource-curator
Find, evaluate, and maintain high-quality external resources for JavaScript concept documentation, including auditing for broken and outdated links
leonardomso
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
anthropics