Skip to content

docs: give the tool surface its own README section - #18

Merged
Steel-tech merged 1 commit into
mainfrom
claude/best-in-class-github-commit-ksgga0
Aug 19, 2026
Merged

docs: give the tool surface its own README section#18
Steel-tech merged 1 commit into
mainfrom
claude/best-in-class-github-commit-ksgga0

Conversation

@Steel-tech

@Steel-tech Steel-tech commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

The rest of this branch landed on main as #17 (squash), so this PR is now just its final commit: the README update.

The tool list had grown past the one-liner tucked under Providers — this promotes it to a Tools section with a per-tool table (bash, one-path read_file, write_file/edit_file with hashline patches, grep/glob, agent, job, todo, ask), states the runtime-owned parallel-safety rule, adds the hashline-edit guarantee to "Why it's different", and closes the pen section with the fan-out it all adds up to.

README-only; no code paths touched.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KoSjfcJPjXpkVLTS2Vxwwr

@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Steel-tech, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ea2ce433-5da3-409d-85d6-f13993ee7d08

📥 Commits

Reviewing files that changed from the base of the PR and between 16be3e5 and da45c21.

📒 Files selected for processing (1)
  • README.md

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

The tool list had grown past the one-liner tucked under Providers:
promote it to a Tools section with a per-tool table, state the
runtime-owned parallel-safety rule, and link the roadmap. Add the
hashline-edit guarantee to "Why it's different" and close the pen
section with the fan-out it all adds up to.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KoSjfcJPjXpkVLTS2Vxwwr
@Steel-tech
Steel-tech force-pushed the claude/best-in-class-github-commit-ksgga0 branch from 3164212 to da45c21 Compare August 19, 2026 05:28
@Steel-tech Steel-tech changed the title Grow the tool surface: durable coordination, hashline edits, one-path read docs: give the tool surface its own README section Aug 19, 2026
@Steel-tech
Steel-tech merged commit 3ffd17c into main Aug 19, 2026
4 of 5 checks passed
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.

2 participants