Add comprehensive custom agents for specialized workflows: - gentoo-sysadmin: Gentoo Linux system administration (OpenRC, Portage) - tdd-test-writer: TDD Ping-Pong workflow implementation - code-reviewer: Code review against strict style guidelines - documentation-writer: Comprehensive project documentation - python-ai-tutor: AI/ML coursework assistant with teaching focus - dotfiles-manager: Dotfiles management with chezmoi Add custom slash commands for quick workflows: - /gentoo-update: Safe Gentoo system update procedure - /tdd-next: Start next TDD test cycle - /style-check: Comprehensive code style validation - /doc-sync: Update all project documentation - /review-pr: Review pull request before merge - /script-install: Install system script with proper permissions Updated .gitignore to properly track agents and commands while excluding session-specific data (plans/, etc.) Added README.md documenting the configuration structure and usage. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2.3 KiB
2.3 KiB
Documentation Sync
Update all project documentation to reflect recent changes.
Documentation Files to Review
Core Documentation
-
README.md - Entry point and quick start
- Is the project description current?
- Are installation steps accurate?
- Do examples still work?
- Are links valid?
-
CLAUDE.md - Project-specific AI context
- Are critical system notes up to date?
- Do file paths still exist?
- Are workflows current?
- Any new gotchas to document?
-
Feature Status/Changelog
- Document new features
- Mark fixed issues as resolved
- Update version numbers if applicable
User Guides
Check each guide in docs/guides/:
- Are commands still correct?
- Do examples work as written?
- Are screenshots up to date (if any)?
- Cross-references still valid?
API Documentation
If applicable:
- Function signatures match implementation?
- Parameter descriptions accurate?
- Return values correct?
- Examples tested?
Troubleshooting
- Add new issues encountered
- Update solutions if procedures changed
- Remove obsolete issues
- Test all diagnostic commands
Update Process
-
Identify changes:
git log --since="1 week ago" --oneline git diff HEAD~10..HEAD --stat -
Check for breaking changes:
- API changes
- Configuration format changes
- Dependency updates
- Command line interface changes
-
Update affected documentation:
- Use the Read tool to check current content
- Use the Edit tool to make precise changes
- Maintain consistent formatting
- Update "Last Modified" dates
-
Verify cross-references:
- Check all links still work
- Update paths if files moved
- Ensure examples reference correct files
-
Test examples:
- Run all code examples
- Verify output matches documentation
- Update if behavior changed
-
Commit documentation updates:
git add docs/ README.md CLAUDE.md git commit -m "docs: sync documentation with recent changes"
Checklist
- README.md reviewed and updated
- CLAUDE.md reflects current state
- All guides checked for accuracy
- Code examples tested
- Cross-references validated
- Breaking changes documented
- Version updated (if applicable)
- Commit message follows conventions