mirror of https://github.com/alirezarezvani/ClaudeForge.git synced 2026-07-03 02:13:15 -04:00

Files

T

Claude 45767e8840 feat(skills): three forked task-style audit skills + /sync-claude-md --weekly orchestration

Three new task-style skills, each using Anthropic's context: fork + agent:
Explore so the work happens in an isolated subagent context and only a
short summary returns to the main session.

skill/claude-md-drift-audit/SKILL.md (51 lines):
  Walks the last N days of git history (default 7) and flags CLAUDE.md
  lines that reference deleted paths, renamed paths, or removed
  dependencies from that window. Returns a punch list with file:line.
  Read-only. Standalone invocation: /claude-md-drift-audit [days=7].

skill/claude-md-link-check/SKILL.md (51 lines):
  Verifies every @path chain import and every relative markdown link
  inside every CLAUDE.md resolves to an existing file. Returns broken
  links with file:line. Read-only. Standalone: /claude-md-link-check
  [path-glob].

skill/claude-md-dependency-rescan/SKILL.md (54 lines):
  Re-detects the project's tech stack from package.json /
  requirements.txt / pyproject.toml / go.mod / Cargo.toml and diffs
  against every CLAUDE.md's Tech Stack section. Returns added /
  removed / renamed per file. Read-only. Standalone:
  /claude-md-dependency-rescan [manifest-path].

command/sync-claude-md.md:
  - argument-hint and when_to_use mention --weekly.
  - New Phase 0 (only when --weekly is passed): invoke the three skills
    above in parallel via the Skill tool, aggregate findings into
    ## Weekly Audit Summary, then proceed to existing Phase 1.
  - Without --weekly, Phase 0 is skipped entirely (no behaviour change
    for normal sync runs).

.claude-plugin/plugin.json:
  skills array now lists all five entries (existing two + three new).

Verified (6/6 smoke tests):
  - Plugin manifest is valid JSON; 5 skills registered; all 8
    referenced paths resolve on disk.
  - Each new SKILL.md parses; context=fork, agent=Explore, both
    description and when_to_use present, allowed-tools is a list,
    body ≤ 60 lines.
  - Each body is imperative (numbered steps present, not reference
    material — fork-context requires explicit task instructions).
  - Sync command body contains Phase 0, all three skill references,
    parallel-invocation language, and Skill in allowed-tools.
  - Skill name in frontmatter matches the directory name for every
    new skill (so /claude-md-drift-audit etc. register correctly).

2026-05-19 02:04:00 +00:00

2.5 KiB

Raw Blame History

name, description, when_to_use, argument-hint, context, agent, allowed-tools, disable-model-invocation

name

description

when_to_use

argument-hint

context

agent

allowed-tools

disable-model-invocation

claude-md-dependency-rescan

Re-detect this project's tech stack from package.json / requirements.txt / pyproject.toml / go.mod / Cargo.toml and diff it against the Tech Stack section of every CLAUDE.md. Read-only — returns added / removed / renamed dependencies, never edits.

Use when the user asks "is my Tech Stack section up to date?", "what deps changed?", "rescan my dependencies", after dependency upgrades, or as part of /sync-claude-md --weekly.

[manifest-path]

fork

Explore

Read

Glob

Grep

Bash(find:*)

Bash(cat:*)

false

CLAUDE.md Dependency Rescan (forked, read-only)

Optional explicit manifest: $ARGUMENTS (default: auto-detect all five manifest types).

Run these steps in order. Do not modify any file.

Detect manifests. Look for package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml at the repo root and one level deep (workspaces/monorepos).
Extract declared dependencies from each:
- package.json → keys of dependencies and devDependencies (skip versions).
- requirements.txt → first token of each non-comment line.
- pyproject.toml → [project.dependencies] / [tool.poetry.dependencies] keys.
- go.mod → module paths under require (...).
- Cargo.toml → keys under [dependencies] / [dev-dependencies].
Inventory documented deps in every CLAUDE.md (and .claude/rules/*.md): grep for the Tech Stack / Dependencies sections and the lists under them.
Compute three sets per file:
- added: in manifest but absent from this CLAUDE.md.
- removed: documented in this CLAUDE.md but absent from manifest.
- renamed: documented and present in manifest but spelled differently (react-router vs react-router-dom, pg vs psycopg2).
Return in this exact shape:

## Dependency Rescan

Manifests detected: <list>
Total declared deps: <count>

### Per file
#### <path-to-CLAUDE.md>
- Added (in manifest, not documented): <list or "none">
- Removed (documented, not in manifest): <list or "none">
- Renamed / aliased: <list or "none">

If every documented set matches its manifest, return exactly ## Dependency Rescan\n\nAll documented deps match manifests. <M> files inspected.. Do not pad.

Hard rule: do not propose specific edits — just surface the diffs. /sync-claude-md decides whether to write them.

2.5 KiB Raw Blame History

CLAUDE.md Dependency Rescan (forked, read-only)

2.5 KiB

Raw Blame History