Skip to content

Conversation

@Ashwinhegde19
Copy link
Contributor

@Ashwinhegde19 Ashwinhegde19 commented Dec 29, 2025

Summary

This PR addresses two critical bugs affecting user experience:

  1. macOS/BSD setup failure - Users on macOS cannot use /conductor:setup due to token limit errors
  2. Missing documentation commits - Documentation updates after track completion are not automatically committed

Changes

1. Fix macOS/BSD compatibility in setup.toml (Issue #11)

  • Problem: The ls -lR -I 'node_modules' command fails silently on macOS/BSD systems because the -I flag is not supported. This causes node_modules and other directories to be scanned, leading to API token limit errors.
  • Solution: Replace with cross-platform find command that works on all systems:
    find . -type d \( -name 'node_modules' -o -name '.m2' -o -name 'build' -o -name 'dist' -o -name 'bin' -o -name 'target' -o -name '.git' -o -name '.idea' -o -name '.vscode' -o -name '__pycache__' \) -prune -o -type f -print | head -200
  • Additional improvement: Added __pycache__ to exclusion list
  • Impact: macOS users can now successfully run /conductor:setup without hitting token limits

2. Add automatic documentation commit step in implement.toml (Issue #16)

  • Problem: After implementing a track, documentation synchronization updates product.md, tech-stack.md, and product-guidelines.md, but these changes are not committed automatically. Users must manually commit these files.
  • Solution: Added new section 7 "Commit Documentation Updates" in implement.toml:
    • Checks if documentation files were modified during synchronization
    • Automatically commits changes with format: conductor(doc-sync): Update documentation for '<track_description>'
    • Skips commit step if no changes were made
  • Section renumbering: Renamed section 7 to 8 (TRACK CLEANUP) and updated execution trigger to include commit requirement
  • Impact: Documentation changes are now automatically committed after track completion, completing the workflow

Testing

Both fixes have been tested and work as expected:

  1. Setup on macOS/BSD now respects directory exclusions
  2. Documentation updates are committed with proper messages

Fixes

- Update gemini-extension.json version from 0.1.0 to 0.1.1 to match latest release
- Add troubleshooting section to README addressing 401 errors during installation
- Document workarounds for GitHub API rate limiting issues (issue gemini-cli-extensions#20)

Fixes gemini-cli-extensions#20
- Fix setup.toml: Replace ls -lR -I with cross-platform find command
  - macOS/BSD ls doesn't support -I flag, causing node_modules to be scanned
  - Use find command with prune option which works on all platforms
  - Add __pycache__ to exclusion list

- Fix implement.toml: Add automatic commit step after documentation synchronization
  - Previously, documentation updates (product.md, tech-stack.md, product-guidelines.md) were not committed
  - Add section 7: Commit Documentation Updates
  - Rename section 7 to 8 (TRACK CLEANUP)
  - Update execution trigger to include commit requirement

Fixes gemini-cli-extensions#11 (setup token limit on macOS) and gemini-cli-extensions#16 (uncommitted files after implementation)
@Ashwinhegde19 Ashwinhegde19 changed the title fix: update version to v0.1.1 and add installation troubleshooting (fixes #20) fix: resolve macOS setup compatibility and add documentation commit step (fixes #11, #16) Dec 29, 2025
@sherzat3
Copy link
Collaborator

sherzat3 commented Jan 7, 2026

Hey @Ashwinhegde19 , thanks for the PR! Good catch on the macOS/BSD incompatibility. On the the missing documentation commit, we actually already fixed that in PR #48.

Feel free to pull the latest changes and update this PR to include only the macOS/BSD compatibility fix, or submit a fresh PR if that's easier.

@sherzat3
Copy link
Collaborator

sherzat3 commented Jan 7, 2026

Fresh PR with the requested changes was started in #56. Closing this PR.

@sherzat3 sherzat3 closed this Jan 7, 2026
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.

/conductor setup fails with "token count exceeds maximum" (400) on large repositories Uncommitted files after implementing a track

3 participants