docs: reorder and trim Key Features in README - #48
Merged
Conversation
Move Key Features up beside Use Cases so the orientation content is grouped ahead of installation and usage. Trim the table to the three headline capabilities (Blame, Git-ref Sync, Cross-tool Memory); the remaining features are already covered by their dedicated sections.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Groups the README's orientation content together and slims the feature table.
Changes
Why
Installation and Quick Start previously sat between Use Cases and Key Features, forcing a reader still evaluating the tool to scroll past install commands to finish understanding it. The dropped table rows (Search, Git Linking, Session Capture, MCP Server, Background Daemon) are already covered by Use Cases, Quick Start, Supported Tools, and the MCP Integration section, so no capability disappears.
Docs-only change: lightweight self-check per project rules (renders correctly, links resolve, no em dashes, factually accurate).