Public-release polish: commercial README, sharper descriptions, repo hygiene#1
Merged
Conversation
- README: reframe around the pain (PRs swarmed by review bots; replying properly is fiddly and easy to get wrong) -> how reply-pr solves it. Hero line, badges, benefit-first bullets, will/won't table, both mermaid diagrams kept. - SKILL.md: lead the description with the value (what lookmi shows) while keeping the trigger phrases; now says "any bot", not just the big three. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughREADME.md and ChangesDocumentation and repository housekeeping
Workspace evaluation cleanup
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Around line 14-17: The README copy overstates the guarantee by claiming “zero
threads unresolved” unconditionally. Update the descriptive text for reply-pr to
say it aims to leave settled threads resolved, while allowing threads to remain
open when waiting on reviewer follow-up or when resolution is premature; keep
the phrasing aligned with the product behavior described in the reply-pr
summary.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 16a4cd41-2f5f-4d02-bb4d-d36e1deb7b1b
📒 Files selected for processing (2)
README.mdskills/reply-pr/SKILL.md
An earlier `git add -A` swept skill-creator's `reply-pr-workspace/` eval output into the repo. Remove it from tracking, gitignore `*-workspace/`, and add a CLAUDE.md rule (verify staged files; never `git add -A` blindly; don't commit local scratch/generated artifacts) so it can't recur. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
thdurante
changed the title
…t the mechanics carry it Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Around line 66-70: Add a language tag to the fenced command block in README so
markdownlint passes; update the existing docs snippet for the /reply-pr examples
to use a bash fence while keeping the commands unchanged. Locate the Markdown
fence around the /reply-pr usage examples and make the minimal formatting change
only.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
CodeRabbit flagged the /reply-pr usage fence as missing a language; tag it bash, and tag the directory-tree block text so the docs are fully lint-clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Polish + hygiene to get reply-pr ready for public / lookmi.
README + description
README.md— a calm, matter-of-fact rewrite: states the problem plainly (a PR gathers comments from several reviewers; replying properly is fiddly) and lets the mechanics carry it. Badges, the two mermaid diagrams (flow + reviewer routing), and a plain does/doesn't table. Deliberately not a landing page.SKILL.md— sharpened thedescriptionto lead with what it does (what lookmi shows on the card) while keeping the trigger phrases; now says "any bot", not just the big three.Repo hygiene
reply-pr-workspace/) that an earliergit add -Aaccidentally committed, gitignored*-workspace/, and added aCLAUDE.mdrule so it can't recur. That scratch is also onmainfrom an earlier commit — merging this PR removes it frommain.GitHub / lookmi short description
Set to:
Triage and reply to a PR's unresolved review comments — reply-only, on each reviewer's channel, with you approving every reply.🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation
Chores