Link docs hierarchy from README and fix broken design references#166
Conversation
The README's Project Structure was a code block, so the link parser saw no outgoing links to the package READMEs. Convert it to a markdown list so packages/sheets, packages/docs, packages/frontend, packages/backend, packages/cli/skills, and packages/documentation are all reachable from the project's entry point. Add a Documentation section linking docs/, MAINTAINING.md, and CLAUDE.md (also exposed as AGENTS.md via symlink). In docs/README.md, the design/ and tasks/ entries used \`(design/)\` and \`(tasks/)\` style targets that lack a \`.md\` extension, so the link checker treated them as non-doc. Point them at the README.md inside each subdirectory. Add docs-docx-import-export.md and template.md to docs/design/README.md so they are reachable from the design index. Link active/README.md and archive/README.md from docs/tasks/README.md (they were referenced inline by code-style paths previously). Add the two pre-todo \`-plan.md\` files (docs-site, docs-arrow-pixel-accuracy) to docs/tasks/archive/README.md under a legacy plans subsection. Link index.md from packages/documentation/README.md so the VitePress landing redirect is reachable. Fix four broken design references in tasks. The relative paths needed one or two more parent hops to reach docs/design/: - archive/2026/04/20260411-docs-table-merge-ux-todo.md - archive/2026/04/20260408-header-footer-todo.md - active/20260325-docs-wordprocessor-todo.md - active/20260325-docs-wordprocessor-lessons.md
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (10)
📝 WalkthroughWalkthroughDocumentation restructuring PR that reorganizes the main README project structure into linked markdown bullets, introduces a Documentation section with architecture and design references, updates documentation navigation to use README.md files, and corrects cross-reference links throughout design and task documents to reflect new file organization in docs subdirectories. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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. Review rate limit: 0/1 reviews remaining, refill in 60 minutes.Comment |
Verification: verify:selfResult: ✅ PASS in 119.1s
Verification: verify:integrationResult: ✅ PASS |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Found via the link connectivity check script being added to second-brain (yorkie-team/second-brain#34).
Before this change, 319 `.md` files in this repo had no incoming link from the README graph. After, only the `.github/` issue/PR templates and the `AGENTS.md → CLAUDE.md` symlink remain (both are by design).
Test plan
Summary by CodeRabbit