Skip to content

Conversation

@jeremyeder
Copy link
Collaborator

Summary

  • Add automated repomap workflow with pre-commit hook and CI validation
  • Create scripts/update-repomap.sh for repomap management
  • Update documentation to reflect automation
  • Add comprehensive scripts documentation in scripts/README.md

What Changed

Automation Added

  1. Pre-commit Hook - Auto-updates .repomap.txt when committing code changes
  2. CI Validation - Ensures repomap stays current on every push/PR
  3. Automation Script - scripts/update-repomap.sh for manual updates and validation

Documentation Updated

  • README.md - Updated development setup with automation steps
  • CLAUDE.md - Added automation sections and CI workflow details
  • docs/patterns/repomap.md - Comprehensive automation documentation
  • scripts/README.md - New documentation for all repository scripts

Benefits

  • ✅ Repomap automatically stays synchronized with code structure
  • ✅ CI blocks merge if repomap is outdated
  • ✅ Clear error messages with dependency installation hints
  • ✅ Developers don't need to remember to update repomap manually

Test Plan

  • Created automation script (scripts/update-repomap.sh)
  • Configured pre-commit hook (.pre-commit-config.yaml)
  • Added CI validation job (.github/workflows/ci.yml)
  • Updated all documentation
  • Tested script error handling (shows helpful dependency messages)

🤖 Generated with Claude Code

jeremyeder and others added 2 commits January 15, 2026 22:46
- Add scripts/update-repomap.sh for automated repomap management
- Add pre-commit hook to auto-update repomap on code changes
- Add CI validation to ensure repomap stays current
- Update documentation (README.md, CLAUDE.md, docs/patterns/repomap.md)
- Add scripts/README.md documenting all automation scripts

The repomap now automatically updates when committing code changes
and CI validates it's current on every push/PR.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Update all package installation commands to use uv
- Update CI workflow to install and use uv
- Update error messages in scripts to recommend uv
- Keep pip only for bootstrapping uv in CI environments

Per project standards: always prefer uv over pip for package management.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant