link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix
Best use case
link-check is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
It is a strong fit for teams already working in Codex.
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix
Teams using link-check 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/link-check/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How link-check Compares
| Feature / Agent | link-check | Standard Approach |
|---|---|---|
| Platform Support | Codex | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix
Which AI agents support this skill?
This skill is designed for Codex.
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.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# Link Check
You verify every `@file` reference in AIWG distributable skills and agents against the full linking contract, producing a structured PASS/WARN/FAIL report per reference. You can run against a single file, a directory, or the full `agentic/code/` corpus, and optionally auto-migrate legacy bare refs to the `@$AIWG_ROOT/` prefix.
## Triggers
- "link check" / "check links" → run against current file or directory
- "link check agentic/code/" → full corpus scan
- "link check --fix" → auto-migrate legacy bare refs
- "any bad links?" → run link-check on current context
- "check for broken @-refs" → run link-check
- "are there any legacy bare refs?" → run link-check, focus on 4b
## Usage
```
/link-check [path] [options]
```
| Argument | Default | Description |
|----------|---------|-------------|
| path | current file or `agentic/code/` | File or directory to check |
| --fix | off | Auto-migrate `@agentic/code/`, `@src/`, `@docs/`, `@tools/` → `@$AIWG_ROOT/` |
| --report | off | Output structured JSON report instead of human-readable |
| --aiwg-only | off | Check only `.aiwg/` refs (skip bare-core and forbidden checks) |
| --fail-on-warn | off | Treat WARN as FAIL (useful for CI) |
## Reference Classification
Each `@<path>` reference is classified per the AIWG linking contract:
| Pattern | Result | Reason |
|---------|--------|--------|
| `@$AIWG_ROOT/<path>` | PASS | AIWG core file, install-relative |
| `@$TOKEN/<path>` — TOKEN set in env | PASS | Registered corpus token |
| `@$TOKEN/<path>` — TOKEN NOT set | WARN | Unknown token — add to `.env` or export |
| `@.aiwg/<path>` — in Tier 1/2 allowlist | PASS | Normalized project memory |
| `@.aiwg/<path>` — not in allowlist | FAIL | Repo-local only — silently fails in user projects |
| `@.claude/<path>` | FAIL | Deployment target — forbidden in distributable source |
| `@agentic/code/<path>` | WARN | Legacy bare ref — use `@$AIWG_ROOT/agentic/code/` |
| `@src/<path>` | WARN | Legacy bare ref — use `@$AIWG_ROOT/src/` |
| `@docs/<path>` | WARN | Legacy bare ref — use `@$AIWG_ROOT/docs/` |
| `@tools/<path>` | WARN | Legacy bare ref — use `@$AIWG_ROOT/tools/` |
| Relative path within component | PASS | Local ref |
## Process
1. **Resolve target path** — single file, directory, or default `agentic/code/`
2. **Build normalized allowlist** — read all `manifest.json` files under `agentic/code/`; collect `memory.creates[*].path`; add Tier 1 entries
3. **Load environment** — check which env vars are set (for `@$TOKEN/` classification)
4. **Extract all `@<path>` refs** — regex: `@[\$\.]?[a-zA-Z0-9_/.\-]+` in each `.md` file
5. **Classify each ref** per the table above
6. **If `--fix`**: rewrite WARN-classified bare legacy refs in-place:
- `@agentic/code/` → `@$AIWG_ROOT/agentic/code/`
- `@src/` → `@$AIWG_ROOT/src/`
- `@docs/` → `@$AIWG_ROOT/docs/`
- `@tools/` → `@$AIWG_ROOT/tools/`
7. **Produce report**
## Output Format
### Human-readable (default)
```
Link Check: agentic/code/addons/aiwg-dev/skills/dev-doctor/SKILL.md
PASS $AIWG_ROOT/agentic/code/addons/aiwg-dev/rules/addon-boundaries.md
PASS .aiwg/AIWG.md (Tier 1, always present)
WARN agentic/code/addons/aiwg-dev/rules/skill-placement.md
→ legacy bare ref; use $AIWG_ROOT/agentic/code/... prefix
FAIL .aiwg/planning/issue-driven-ralph-loop-design.md
→ non-normalized .aiwg/ path (repo-local only)
Result: 2 issues (1 WARN, 1 FAIL)
```
### Corpus summary
When run against a directory:
```
Link Check: agentic/code/ (corpus-wide)
Files checked: 247
References found: 1,341
PASS: 1,337
WARN: 3
FAIL: 1
Violations:
WARN agentic/code/addons/my-addon/skills/my-skill/SKILL.md:42
agentic/code/... (bare ref) → add $AIWG_ROOT/ prefix
FAIL agentic/code/addons/my-addon/skills/my-skill/SKILL.md:89
.aiwg/planning/my-design.md → non-normalized (repo-local only)
Overall: WARN (3 warnings, 1 failure)
Run with --fix to auto-migrate WARN refs.
```
### JSON report (`--report`)
```json
{
"target": "agentic/code/",
"timestamp": "2026-04-01T04:48:00Z",
"summary": { "files": 247, "refs": 1341, "pass": 1337, "warn": 3, "fail": 1 },
"violations": [
{
"file": "agentic/code/addons/my-addon/skills/my-skill/SKILL.md",
"line": 42,
"ref": "agentic/code/addons/aiwg-dev/rules/skill-placement.md",
"result": "WARN",
"message": "legacy bare ref — add $AIWG_ROOT/ prefix",
"fix": "$AIWG_ROOT/agentic/code/addons/aiwg-dev/rules/skill-placement.md"
}
]
}
```
## Auto-Fix Behavior (`--fix`)
Only WARN-classified legacy bare refs are auto-fixed. FAIL refs (repo-local `.aiwg/` paths, `.claude/` refs) are **never auto-fixed** — they require a human decision:
- Remove the reference
- Replace with a normalized equivalent
- Or normalize the path in a manifest's `memory.creates`
After `--fix`, report how many refs were migrated and re-run the check to confirm the result.
## CI Integration
Use `--report --fail-on-warn` for CI:
```bash
# Fails if any FAIL or WARN refs found
aiwg link-check agentic/code/ --report --fail-on-warn > link-report.json
```
Exit codes:
- `0` — all PASS
- `1` — WARN found (only if `--fail-on-warn`)
- `2` — FAIL found
## Examples
### Check a single skill
**User**: "check links in the dev-doctor skill"
**Action**: Run link-check on `agentic/code/addons/aiwg-dev/skills/dev-doctor/SKILL.md`.
### Full corpus check
**User**: "any bad links in the corpus?"
**Action**: Run link-check on `agentic/code/` and summarize violations.
### Auto-fix
**User**: "link check --fix"
**Action**: Run link-check on `agentic/code/`, migrate all bare legacy refs, report how many were fixed.
## References
- @$AIWG_ROOT/agentic/code/addons/aiwg-dev/rules/aiwg-dir-reference-contract.md — Full linking contract
- @$AIWG_ROOT/agentic/code/addons/aiwg-dev/skills/validate-component/SKILL.md — Per-component validation
- @$AIWG_ROOT/agentic/code/addons/aiwg-dev/skills/dev-doctor/SKILL.md — Full repo health checkRelated Skills
eslint-checker
Run ESLint for JavaScript/TypeScript code quality and style enforcement. Use for static analysis and auto-fixing.
traceability-check
Verify bidirectional traceability from requirements to code to tests and identify coverage gaps and orphan artifacts
regression-check
Compare current behavior against baseline to detect regressions
quality-checker
Validate skill quality, completeness, and adherence to standards. Use before packaging to ensure skill meets quality requirements.
project-health-check
Analyze overall project health and metrics
flow-handoff-checklist
Orchestrate handoff validation between SDLC phases and tracks (Discovery→Delivery, Delivery→Ops, phase transitions)
flow-gate-check
Orchestrate SDLC phase gate validation with multi-agent review and comprehensive reporting
citation-check
Check a file for citation quality and GRADE compliance
checkpoint
Create, list, or recover mid-workflow checkpoints so interrupted work resumes from a known-good position
check-traceability
Verify the full refinement chain from use cases through behavioral specs, pseudo-code specs, code, and tests — report coverage at each layer and identify gaps
check-completeness
Analyze collection completeness against canonical discography and generate prioritized gap report
aiwg-orchestrate
Route structured artifact work to AIWG workflows via MCP with zero parent context cost