customize-status

Customize Status

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.

Triggers

• "what have I customized?"
• "show my changes"
• "what's my AIWG setup?"
• "am I in customize mode?"
• "customization status"
• "what does my AIWG look like?"
• "how different is my AIWG from the default?"

Trigger Patterns Reference

Behavior

When triggered:

1. 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.

2. Load edgePath from config (or parse from aiwg version output).

3. Detect fork vs clone — check if upstream remote exists:

   git -C <edgePath> remote -v
   

4. 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.

5. 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
   

6. 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