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.

9 stars 2 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add boweneos/repo-wiki-agent-skills --skill repo-wiki-detect
Manual install
git clone --depth 1 https://github.com/boweneos/repo-wiki-agent-skills.git /tmp/repo-wiki-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/repo-wiki-agent-skills/repo-wiki-detect ~/.claude/skills/repo-wiki-detect

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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:

1. Files added, modified, deleted, or renamed
2. Components affected by changes
3. Documentation pages that need updates
4. 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

```bash
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

```bash
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:
Read the full skill on GitHub

Details

Skill name
repo-wiki-detect
Path
repo-wiki-detect/SKILL.md
License
MIT
Repo updated
26 February 2026

FAQ

What does the Repo Wiki Detect skill do?

Detect code changes since last wiki update using git diff. Identifies added, modified, deleted, and renamed files to determine which documentation pages need updates.

How do I install the Repo Wiki Detect skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add boweneos/repo-wiki-agent-skills --skill repo-wiki-detect. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Repo Wiki Detect popular?

It lives in boweneos/repo-wiki-agent-skills, which has 9 GitHub stars and 2 forks.

Related skills

Repo Wiki

9

boweneos/repo-wiki-agent-skills

Generate and maintain citation-backed repository wikis as MkDocs-compatible Markdown. Creates baseline docs, detects changes, and incrementally updates only affected pages with file path and line number citations.

Research & Science

Repo Wiki Generate

9

boweneos/repo-wiki-agent-skills

Generate citation-backed documentation pages from code index. Creates markdown content with file path and line number citations for every technical claim.

Research & Science

Repo Wiki Index

9

boweneos/repo-wiki-agent-skills

Build a searchable code map of the repository. Extracts modules, components, APIs, configs, dependencies, and key symbols for documentation and citation purposes.

Frontend & Design

Zephyr Explore

9

processmission/agent-skills

Use when Zephyr source, branch history, external precedent, or design constraints must be investigated before a decision can be made.

Git & Code Review

Push Check

10

charlie947/skills-for-everyone

Check everything before work goes to GitHub, then push it. Runs the repo's own checks, a sweep for leaked keys, personal paths, oversized files and dead links, a second Claude reading the changes cold, and a fresh-copy rehearsal of what a new user does first. Pushes only after two clean passes in a row, then drafts the short note to send people, if there is anything for them to do. Use when the user says "push", "push this", "ship it", "put it on GitHub", "release", "send it to them", "is it ready to push", or is about to share a repo other people will download.

Git & Code Review

Design Review

9

eralmansouri/skills

Design review of a codebase area, branch, or PR. Maps its bounded contexts, vertical slices, and modules, then judges where rules live and whether flexibility sits where change actually happens. Use when the user asks for a design or architecture review, or when a review should judge structure rather than bugs or style.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.