Repository navigation
docs: point docs at their sources instead of restating them - #8
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: musingfox/better-link/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (4)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthrough此變更更新 CodeRabbit 的檔案規則,新增架構文件,並修訂專案說明及 CPU 預算規格中的驗證、計時與超標資訊。 Changes文件與審查規則
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This PR updates project guidance and CPU-budget documentation without changing Worker behavior. The concerns raised do not violate applicable project requirements, so no material merge risk remains. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 3 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
a73f4fd to
3c309cc
Compare
…ts sources The spec said no runnable check existed, but the parser tests already time the fixtures and fail above 10 ms, so verify now runs them. It also pointed at a step of a design doc that lives outside the repo; name where Cloudflare reports CPU overruns instead, and record the 8–9 ms cold-fetch peaks measured with wrangler tail, which the 1–2 ms figure alone understated. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The guide's summary of clean.ts had already missed the Threads xmt rule. The codemap now names modules and points at the specs for their rules, and the guide keeps one pointer to it and one to the README. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
CLAUDE.md summarized each spec and CodeRabbit's path instructions restated them again, so every spec change needed three edits. CodeRabbit applies guideline files only to their own directory unless mapped with applyTo, which is why the restatement existed; map docs/spec onto the files in each scope instead. CLAUDE.md is a default guideline file and no longer needs listing. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
7f998ad to
7ab97a2
Compare
Summary
Doc audit follow-up, stacked on #7.
cpu-budget-10ms:verifynow runs the parse timing tests. With a 15 ms busy loop added toparseVideoPage, two tests failed, so the check does catch a slow parser.ARCHITECTURE.md, and CLAUDE.md keeps one pointer to it.knowledge_basemapsdocs/spec/*.mdonto the files each spec constrains withapplyTo. WithoutapplyTo, CodeRabbit applies a guideline file only to its own directory.bun.lockrule is shortened to one clause that namestest/config.test.ts.Test plan
bun run checkpasses on every commit.verifycommand passes.🤖 Generated with Claude Code
Summary by CodeRabbit