docs: clarify contribution fit#545
Conversation
📝 WalkthroughWalkthroughThis PR adds initial ChangesContribution Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Greptile SummaryAdds contributor documentation: a root
Confidence Score: 5/5Documentation-only change with no runtime, data, or configuration impact. All three files are purely documentation. The root redirect, the contributing guide content, and the sidebar config change are all straightforward and consistent with the rest of the project's conventions. No files require special attention. Important Files Changed
Reviews (8): Last reviewed commit: "docs: make contributing guide canonical" | Re-trigger Greptile |
| mise install | ||
| ``` | ||
|
|
||
| Run the checks listed in the repository before opening a PR. |
There was a problem hiding this comment.
The phrase "the checks listed in the repository" is ambiguous —
CLAUDE.md already documents the exact command (mise run ci). Pointing contributors directly to that command (or to CLAUDE.md) removes any guesswork.
| Run the checks listed in the repository before opening a PR. | |
| Run `mise run ci` (build + test + lint) before opening a PR. See `CLAUDE.md` for the full list of available commands. |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
🧹 Nitpick comments (1)
CONTRIBUTING.md (1)
20-20: ⚡ Quick winClarify which specific checks contributors should run locally.
The phrase "checks listed in the repository" is vague and may leave contributors uncertain about which commands to run. The mise.toml file defines several tasks (test, lint, build), and
mise run ciruns all of them together. Explicitly mention the command(s) contributors should execute before opening a PR.💡 Suggested improvement
Run the checks listed in the repository before opening a PR. + Run `mise run ci` to execute the full check suite (build, test, lint).Alternatively, list individual commands:
Run the checks listed in the repository before opening a PR. + + ```sh + mise run ci # Run build, test, and lint + ``` + + Or run individual steps: + - `mise run build` to build the project + - `mise run test` to run tests + - `mise run lint` to check code style and quality🤖 Prompt for 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. In `@CONTRIBUTING.md` at line 20, Replace the vague sentence "Run the checks listed in the repository before opening a PR." with explicit commands: ask contributors to run `mise run ci` (which executes build, test, and lint) or, optionally, run individual tasks `mise run build`, `mise run test`, and `mise run lint` locally; include a short example snippet showing `mise run ci` and the three individual commands so it's unambiguous which checks are required.
🤖 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.
Nitpick comments:
In `@CONTRIBUTING.md`:
- Line 20: Replace the vague sentence "Run the checks listed in the repository
before opening a PR." with explicit commands: ask contributors to run `mise run
ci` (which executes build, test, and lint) or, optionally, run individual tasks
`mise run build`, `mise run test`, and `mise run lint` locally; include a short
example snippet showing `mise run ci` and the three individual commands so it's
unambiguous which checks are required.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 4989694d-6547-45e0-bbbe-5251344c9d3f
📒 Files selected for processing (1)
CONTRIBUTING.md
f071edd to
563ffd1
Compare
563ffd1 to
2f897a5
Compare
Summary
Tests
Note
Low Risk
Documentation-only changes with no runtime or security impact.
Overview
Adds contributor-facing documentation: a root
CONTRIBUTING.mdthat points readers to the published site guide, and a newdocs/contributing.mdpage with expectations (scope, Discord, CI/AI review gates, rejection policy), plus hk/mise workflow, Conventional Commits, testing, and development setup.The VitePress Introduction sidebar now includes a Contributing link to
/contributing.Reviewed by Cursor Bugbot for commit 0706ba0. Bugbot is set up for automated code reviews on this repo. Configure here.