customize-status
Show current AIWG customization status — mode, source path, what you've customized vs upstream
Best use case
customize-status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Show current AIWG customization status — mode, source path, what you've customized vs upstream
Teams using customize-status should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/customize-status/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How customize-status Compares
| Feature / Agent | customize-status | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Show current AIWG customization status — mode, source path, what you've customized vs upstream
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
| 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 |
## Behavior
When triggered:
1. **Check current mode**:
```bash
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:
```bash
git -C <edgePath> remote -v
```
4. **Summarize customizations** — files the user added or modified vs what's in the repo:
```bash
# 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):
```bash
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
```
If no customizations yet:
```
Your customizations: none yet
Try: "add a rule that [something personal]" then "apply my changes"
```
## Examples
### Example 1: Full status check
**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.
### Example 2: Quick mode check
**User**: "am I in customize mode?"
**Action**: `aiwg version`
**Response**: "Yes — AIWG is running from ~/my-aiwg [dev mode]. You have 2 customizations."
### Example 3: Not in customize mode
**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."
## Clarification Prompts
None needed — report what you find.
## References
- @$AIWG_ROOT/src/channel/manager.mjs — `loadConfig()` for edgePath and channel
- @$AIWG_ROOT/docs/customization/README.md — Customization guideRelated Skills
customize-upstream-sync
Pull the latest upstream AIWG updates into the user's fork and rebuild — preserves user customizations
customize-setup
Set up personal AIWG customization mode from a local clone or fork — makes your clone the live global AIWG instance so edits go live immediately
customize-rebuild
Rebuild and redeploy AIWG from local customization source — makes recent edits live
customize-contribute-back
Contribute a user's AIWG customization back upstream as a PR — reviews for general applicability, creates branch, opens PR
soul-status
Show SOUL.md enforcement state across all installed providers with quality check
rlm-status
Show status of RLM task tree execution
research-status
Show research corpus health and statistics
ralph-status
Check status of current or previous agent loop
project-status
Analyze project state from .aiwg/ artifacts and provide contextual status with recommended next steps
plugin-status
List installed Claude Code plugins with version, install date, and enabled status
pipeline-status
Show status overview of all LLM inference pipelines in the current project
marketing-status
Project directory path (default current directory)