Repository navigation
Generated Reference Signposts (Cycle 0027) - #14
Conversation
Generate CLI.md and MCP.md from source code during ship sync.
- CLI.md generated from CLI_TOPICS + usage() in cli-args.ts - MCP.md generated from MCP_TOOLS array in mcp.ts - Both carry generated_from_commit SHA in frontmatter - MCP tool definitions extracted to shared MCP_TOOLS export - CLI topics exported as CLI_TOPICS constant - shipSync now regenerates CLI.md and MCP.md on every run - Ship sync for cycle 0026 included 122 tests pass.
Hill met. CLI.md and MCP.md now generated from source during ship sync. 122 tests pass. No drift.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 1 minutes and 30 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (11)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c5d29417b1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| private currentCommitSha(): string { | ||
| try { | ||
| return execSync('git rev-parse HEAD', { cwd: this.root, encoding: 'utf8', stdio: ['pipe', 'pipe', 'pipe'] }).trim(); |
There was a problem hiding this comment.
Use current tree id for generated_from_commit
shipSync() stamps docs with git rev-parse HEAD, which is always the last committed revision, not the workspace state that actually produced the regenerated files. In the normal flow (edit code, run method sync ship, then commit), docs/CLI.md and docs/MCP.md will record a commit that can predate the command/tool definitions they contain, so provenance-based drift checks can be misled. Please derive this value from the current tree/workspace state instead of pre-sync HEAD.
Useful? React with 👍 / 👎.
Summary
CLI.md and MCP.md are now generated from source code during
method sync ship:CLI_TOPICS+usage()incli-args.tsMCP_TOOLSarray inmcp.tsgenerated_from_commitSHA in frontmatterAlso includes ship sync for cycle 0026 (CHANGELOG + BEARING).
Test plan
method sync shipregenerates both docs