$npx -y skills add lbb00/ai-rules-sync --skill update-docsUpdate all project documentation after code changes.
| 1 | # Update Documentation |
| 2 | |
| 3 | ## Instructions |
| 4 | |
| 5 | One-click command to update all project documentation after code changes. |
| 6 | |
| 7 | ### Steps |
| 8 | |
| 9 | 1. **Analyze Changes** |
| 10 | - Check git status for modified files |
| 11 | - Review recent commits if no uncommitted changes |
| 12 | - Identify what documentation needs updating |
| 13 | |
| 14 | 2. **Update KNOWLEDGE_BASE.md** |
| 15 | - Run the `update-knowledge-base` skill |
| 16 | - Document any architectural or feature changes |
| 17 | |
| 18 | 3. **Update README.md** |
| 19 | - Add new features or commands |
| 20 | - Update examples if API changed |
| 21 | - Ensure accuracy of all documented commands |
| 22 | |
| 23 | 4. **Sync README_ZH.md** |
| 24 | - Run the `sync-readme` skill |
| 25 | - Ensure Chinese documentation matches English |
| 26 | |
| 27 | 5. **Verify** |
| 28 | - Run tests to ensure nothing broken: `npm test` |
| 29 | - Check that all documented commands work |
| 30 | - Review diff before committing |
| 31 | |
| 32 | ### When to Use |
| 33 | |
| 34 | - After adding a new adapter |
| 35 | - After adding or modifying CLI commands |
| 36 | - After changing the configuration format |
| 37 | - After any user-facing changes |
| 38 | |
| 39 | ### Output |
| 40 | |
| 41 | All documentation files updated and in sync: |
| 42 | - KNOWLEDGE_BASE.md (if exists) |
| 43 | - README.md |
| 44 | - README_ZH.md |
| 45 | |
| 46 | ## Examples |
| 47 | |
| 48 | Request: Update all docs after adding OpenCode support |
| 49 | Result: KNOWLEDGE_BASE.md, README.md, and README_ZH.md all updated |