docs: add AI usage policy for contributors#547
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded a new repository-level Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
AI_POLICY.md (1)
66-68: Optional wording polish for readability.Line 67 can be tightened by replacing “whether or not” with “whether” to reduce verbosity while keeping meaning intact.
Suggested edit
-preoccupied with whether or not they could, they didn't stop to think +preoccupied with whether they could, they didn't stop to think🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@AI_POLICY.md` around lines 66 - 68, Replace the phrase "whether or not" with "whether" in the sentence quoting Ian Malcolm (the line containing "they were so preoccupied with whether or not they could, they didn't stop to think if they should") to tighten wording while preserving meaning and punctuation.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@AI_POLICY.md`:
- Line 54: Replace the incorrect singular verb in the sentence containing the
phrase "Parts of Grimmory has been written with AI assistance, and many
maintainers" by changing "has" to "have" so the sentence reads "Parts of
Grimmory have been written with AI assistance, and many maintainers"; update
that occurrence in AI_POLICY.md.
---
Nitpick comments:
In `@AI_POLICY.md`:
- Around line 66-68: Replace the phrase "whether or not" with "whether" in the
sentence quoting Ian Malcolm (the line containing "they were so preoccupied with
whether or not they could, they didn't stop to think if they should") to tighten
wording while preserving meaning and punctuation.
🪄 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: 2ad1fb60-454a-4f6b-bc03-f1c6a2c287a4
📒 Files selected for processing (1)
AI_POLICY.md
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Test Suite / Backend Tests
🧰 Additional context used
🪛 LanguageTool
AI_POLICY.md
[style] ~67-~67: Consider shortening this phrase to just ‘whether’, unless you mean ‘regardless of whether’.
Context: ... Park: _[they] were so preoccupied with whether or not they could, they didn't stop to think i...
(WHETHER)
🔇 Additional comments (1)
AI_POLICY.md (1)
3-40: Strong policy framing and clear contributor expectations.This section is clear, enforceable, and consistent with the stated PR objective. Nice balance between disclosure requirements and human accountability.
Co-authored-by: James Ward <james@notjam.es>
There was a problem hiding this comment.
🧹 Nitpick comments (1)
AI_POLICY.md (1)
66-68: Optional wording polish for readability.Line 67 reads a bit cleaner with “whether” instead of “whether or not”.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@AI_POLICY.md` around lines 66 - 68, Update the quoted Jurassic Park line in AI_POLICY.md (the sentence starting "they were so preoccupied with whether or not they could...") to use “whether” instead of “whether or not” so it reads: "they were so preoccupied with whether they could, they didn't stop to think if they should", preserving the existing emphasis/italics and punctuation.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@AI_POLICY.md`:
- Around line 66-68: Update the quoted Jurassic Park line in AI_POLICY.md (the
sentence starting "they were so preoccupied with whether or not they could...")
to use “whether” instead of “whether or not” so it reads: "they were so
preoccupied with whether they could, they didn't stop to think if they should",
preserving the existing emphasis/italics and punctuation.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 9ad0d58a-7086-43e4-b481-0848b7cbbca5
📒 Files selected for processing (1)
AI_POLICY.md
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
- GitHub Check: Test Suite / Frontend Tests
- GitHub Check: Test Suite / Backend Tests
- GitHub Check: Analyze (java-kotlin)
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: Frontend Lint Threshold Check
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
Repo: grimmory-tools/grimmory PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-26T16:52:56.437Z
Learning: Create agent-related documentation and guidelines in AGENTS.md
🪛 LanguageTool
AI_POLICY.md
[style] ~67-~67: Consider shortening this phrase to just ‘whether’, unless you mean ‘regardless of whether’.
Context: ... Park: _[they] were so preoccupied with whether or not they could, they didn't stop to think i...
(WHETHER)
🔇 Additional comments (1)
AI_POLICY.md (1)
54-55: Fix subject–verb agreement in this sentence.Line 54 should use plural agreement: “Parts of Grimmory have been written…”.
Suggested edit
-Parts of Grimmory has been written with AI assistance, and many maintainers +Parts of Grimmory have been written with AI assistance, and many maintainers
Co-authored-by: James Ward <james@notjam.es>
Description
This PR adds a repo-level AI usage policy for contributors. This policy was formed by reflecting on the AI policies instituted by other popular FOSS projects. This specific policy is adapted from the Ghostty AI Usage Policy.
The new policy sets expectations for disclosure, review, testing, and human accountability
when AI tools are used in discussions, issues, or pull requests. It also explicitly
disallows AI-generated media in contributions, and gives maintainers a clear set of rules for
handling low-effort or unreviewed AI submissions.
Changes
Summary by CodeRabbit