-
Notifications
You must be signed in to change notification settings - Fork 2
commit
name: commit description: Commit wiki changes after verifying all links are valid user-invocable: true
Before committing, verify that every markdown link in the wiki resolves to an existing file.
-
Run
go run bin/check-links.gofrom the wiki root directory. If it reports any broken or stale references, show them to the user and stop — do NOT proceed to commit. -
If the link check passes, run
git statusandgit diff --statto understand what changed. -
Run
git log --oneline -3to match the existing commit message style. -
Generate a single bash script block that the user can review and run. The script must:
- Use
git addfor each new or modified file (list files explicitly, never usegit add -Aorgit add .) - Use
git rmfor files that were deleted (if any show ingit statusas deleted) - Use
git commit -m "..."with a concise message summarising the changes - Append
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>to the commit message
- Use
-
Present the script to the user in a fenced code block. Do NOT execute it — let the user review and run it themselves.
If links are broken:
Link check failed — fix these before committing:
BROKEN: <file>:<line> -> <target>
...
If links are clean, output the bash script:
#!/usr/bin/env bash
set -e
git add file1.md file2.md ...
git rm old-file.md ...
git commit -m "$(cat <<'EOF'
<commit message>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
EOF
)"Unreviewed draft. This wiki was authored in bulk and has not been reviewed. File corrections on the issue tracker.
- Overview
- YANG Model
- Editor Workflow
- Archive and Rollback
- System
- Interfaces
- BFD
- FIB
- Firewall
- Traffic Control
- L2TP/PPP
- VPP Data Plane
- RPKI
- TACACS+ AAA
- Fleet
- BGP
- Starting and Stopping
- Show Commands
- Monitoring
- Logging
- Operational Reports
- Healthcheck
- MRT Analysis
- Upgrade and Restart
- Storage
- Policy
- Core
- Resilience
- Validation
- Capabilities
- Address Families
- Protocol
- Subsystems
- Infrastructure
- Route Server at an IXP
- Transit Edge with RPKI
- Public Looking Glass
- ExaBGP Migration Walkthrough
- FlowSpec Injection
- Chaos-Tested Peering
- AS Path Topology