Contribution Guide and Code Review Standards Review
Check that expectations for contributors are clear.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review contributor docs. Contribution guide and review checklist: [CONTRIBUTION_DOCS]. Check how to set up, branch naming, commit messages, tests required, review expectations, response time, style rules and a code of conduct. Look for contradictions with actual practice described: [ACTUAL_PRACTICE]. Return a table of gaps, a one-page checklist for authors and reviewers, and a plan to keep the guide current. Add a worked checklist for a contributor: fork, create a branch named feature-short-description, run tests, add tests for changes, write a commit message in the imperative under 70 characters, open a pull request using the template, respond to review within a few days. Reviewers: check tests, naming, security, documentation, and kindness of tone. Add an expected response time, such as a first review within two working days, and note where practice differs from what is written. Add a short section on kindness and clarity in review comments: describe the issue, explain why, suggest a fix, and mark whether it blocks merging. Provide five example comments, three good and two to rewrite.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.