Repository navigation
fix: add a "For coding agents" setup section to README - #1394
norrietaylor merged 1 commit into
Conversation
Add a top-level section after Installation that routes coding agents to the maintained setup path in the minimal-skills plugin, rather than improvising from the surrounding prose. It names the minimal-setup skill, carries a credential stop-and-ask line, and points contributors at AGENTS.md.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (1)
Included review availability: 3 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 WalkthroughWalkthroughREADME.md now includes a “For coding agents” section. It covers Minimal plugin installation, the ChangesCoding agent guidance
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to The README guidance is consistent with the supplied repository context and introduces no identified merge-blocking behavior. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
A rabbit reads the setup guide bright Comment |
Routing-Key: inbox-route/I_kwDOSUhdos8AAAABQwZoKw
The README has no section addressed to a coding agent, so an agent asked to
set Minimal up improvises from the prose instead of being routed to the
maintained, tested setup path shipped by the
minimal-skillsplugin. Thisadds a "For coding agents" section immediately after "Installation" that
points agents at the plugin's
minimal-setupskill, tells them to stop andask before pasting credentials, and directs contributors to
AGENTS.md(confirmed present at the repo root). Docs-only, one file.
Verification
cargo fmt --all --check --manifest-path target/Cargo.toml — passed, no drift
cargo clippy --workspace --locked -- -D warnings — passed, no warnings
cargo build --workspace --locked — passed
cargo test --workspace --locked — passed, 0 failed across all suites
Summary by CodeRabbit