plugins/utils/skills/customize-status/SKILL.md
Show current AIWG customization status — mode, source path, what you've customized vs upstream
npx skillsauth add jmagly/aiwg customize-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You report the current AIWG customization status: whether the user is in customization mode, what path their AIWG runs from, how many customizations they've made, and whether upstream has new commits they haven't pulled yet.
| Pattern | Example | Action |
|---------|---------|--------|
| Mode check | "am I in customize mode?" | aiwg version check |
| Changes summary | "what have I customized?" | git diff vs upstream |
| Full status | "customization status" | Full report |
When triggered:
Check current mode:
aiwg version
Look for [dev] in output and the edgePath. If not in dev mode, report that and offer to run customize-setup.
Load edgePath from config (or parse from aiwg version output).
Detect fork vs clone — check if upstream remote exists:
git -C <edgePath> remote -v
Summarize customizations — files the user added or modified vs what's in the repo:
# If fork (upstream remote exists):
git -C <edgePath> diff upstream/main --name-only -- agentic/code/ .claude/
# If local clone only:
git -C <edgePath> status --short -- agentic/code/ .claude/
Group by type: rules, agents, skills, prompts.
Check upstream staleness (fork mode only):
git -C <edgePath> fetch upstream --dry-run 2>&1 | grep -c "^From" || echo "0"
git -C <edgePath> rev-list HEAD..upstream/main --count
Report in plain language:
AIWG Customization Status
Mode: live (fork)
Source: ~/my-aiwg
Fork: github.com/user/aiwg
Upstream: github.com/jmagly/aiwg — 3 commits ahead
Your customizations (4 files):
rules/ my-conventions.md (3 days ago)
team-style.md (1 week ago)
agents/ domain-specialist.md (2 days ago)
skills/ my-shortcuts/SKILL.md (1 day ago)
→ Say "apply my changes" to redeploy
→ Say "sync my AIWG" to pull the 3 upstream commits
If no customizations yet:
Your customizations: none yet
Try: "add a rule that [something personal]" then "apply my changes"
User: "what have I customized?"
Action: aiwg version → git remote -v → git diff upstream/main --name-only → git rev-list HEAD..upstream/main --count
Response: Full status report as above.
User: "am I in customize mode?"
Action: aiwg version
Response: "Yes — AIWG is running from ~/my-aiwg [dev mode]. You have 2 customizations."
User: "customization status"
Action: aiwg version → not in dev mode
Response: "AIWG is running from the npm package (not in customization mode). Say 'set up AIWG customization mode' to get started."
None needed — report what you find.
loadConfig() for edgePath and channeldata-ai
Report which research-corpus radar sidecars are overdue for refresh. Computes staleness (days since last refresh vs the cadence window) for every radar, sorted most-overdue-first. Runs via `aiwg corpus radar-status`.
data-ai
Aggregate research-corpus radar sidecars into a corpus or per-cluster freshness report — totals, overdue count, per-cluster / per-GRADE / per-trajectory breakdowns, an overdue table, and per-radar rationale snippets. Runs via `aiwg corpus radar-report`.
testing
Scaffold radar/freshness sidecars for research-corpus REFs. Pulls title/authors from the citation sidecar and GRADE from the analysis doc, defaults the refresh cadence from GRADE and the cluster from a corpus-local map, and stamps documentation/radar/REF-XXX-radar.md. Runs via `aiwg corpus radar-init`.
data-ai
Compute an entity's publication trajectory — per-year paper counts, topic drift, hot-streak detection (≥3 consecutive A-grade years), and career phase. Runs via `aiwg corpus profile-temporal`.