From forge-core
Check the forge ecosystem for staleness — installed skills vs source, binary freshness, lib consistency, version drift, submodule pointers, hook config. USE WHEN stale, freshness, out of date, check staleness, need to rebuild, make install needed, system check.
npx claudepluginhub n4m3z/forge-coreThis skill uses the workspace's default tool permissions.
Quick diagnostic that answers: "is everything current, or do I need to `make install`?"
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
Quick diagnostic that answers: "is everything current, or do I need to make install?"
Checks six staleness vectors across the forge ecosystem and produces a pass/fail summary with actionable fixes.
system-check.sh in this skill directory implements all six checks. Run it first:
bash "${FORGE_MODULE_ROOT:-Modules/forge-core}/skills/SystemCheck/system-check.sh"
For per-item breakdown, add --verbose:
bash "${FORGE_MODULE_ROOT:-Modules/forge-core}/skills/SystemCheck/system-check.sh" --verbose
Run the companion script (compact mode).
Present the output table to the user as-is.
If any check fails, the script prints a Fixes: section. Offer to run the suggested commands.
If the user asks to drill down into a specific check, re-run with --verbose and explain the details.
If the script is unavailable or a check needs manual investigation, use the check procedures below.
Read .claude/skills/.manifest (written by forge install) to determine which module owns each installed skill. For each entry, compare the installed SKILL.md body against its source using shasum -a 256 (strip frontmatter first — forge install merges claude: keys, so frontmatter will differ by design).
Three failure modes:
.manifestFalls back to directory scanning if .manifest is absent.
For each symlink in ~/.local/bin that points into the forge root, find the crate's src/ directory and compare the binary mtime against the newest .rs source file. If any source is newer, the binary is stale.
Verify that the forge binary is on PATH and responds to forge --version. Report the installed version.
For each module, read version from up to three sources and report mismatches within a module:
| Source | How to read |
|---|---|
module.yaml | awk '/^version:/{print $2; exit}' |
plugin.json | python3 -c "import json; print(json.load(open('plugin.json'))['version'])" |
Cargo.toml | awk -F'"' '/^version/{print $2; exit}' |
Compare the parent repo's recorded submodule pointer against each submodule's actual HEAD. A + prefix in git submodule status means the submodule HEAD has moved beyond the recorded pointer. A - means not initialized.
Read .claude/settings.json and verify all expected dispatch events are present:
SessionStart, PreToolUse, PostToolUse, Stop, PreCompact, UserPromptSubmit, SubagentStop, SessionEnd, Notification
| Problem | Fix |
|---|---|
| Skills stale | make install |
| Binaries stale | make build && make install-binaries |
| forge CLI missing | Install forge-cli: cargo install forge-cli |
| Version drift | Align versions in the affected module |
| Submodule pointers dirty | Commit parent repo |
| Hook config incomplete | make install-hooks |
shasum -a 256 (macOS compatible), not sha256sumgit -C directly for submodule operations (RTK does not support -C)