[jdx]

The rule that restricted who may use AI to reply to Discussions and Issues, backed by a ban across jdx's projects, is not working and scares people away. This removes it from the repo.

Removed:

• the CAUTION callout in CONTRIBUTING.md
• the ::: danger block in docs/contributing.md
• the "Restricted AI Replies" section in AGENTS.md

Kept: AI-assisted content is still reviewed by the user before it is posted, and it still carries the *AI-assisted — Tool: ...* disclosure. The contributing guide now says that using AI to help write a Discussion, Issue, reply, or pull request is fine.

The same change is going into the other jdx repos.

AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: 2.1.309.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only policy change with no runtime, auth, or data-handling impact.

Overview
This PR drops the policy that only certain contributors could use AI to reply on GitHub Discussions and Issues, along with the instant-ban language across jdx projects.

Removed from AGENTS.md, CONTRIBUTING.md, and docs/contributing.md: eligibility checks (thread author, fixing PR, merged contribution), agent instructions not to post or sweep threads, and the danger/CAUTION callouts.

Unchanged expectations: contributors still review AI-assisted GitHub content before posting and append the *AI-assisted — Tool: …* disclosure. The public contributing guide now states plainly that using AI to help write a Discussion, Issue, reply, or PR is allowed.

^{Reviewed by Cursor Bugbot for commit cea400b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Summary by CodeRabbit

• Documentation
  • Updated contribution guidelines to allow AI-assisted drafts for Discussions, Issues, replies, and pull requests, provided contributors review content before posting and disclose AI assistance.
  • Removed previous restrictions and warnings related to AI-generated replies.

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Central YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 36f48107-964f-4394-8f8b-1f969410fe37

Commits

Reviewing files that changed from the base of the PR and between b15054a and cea400b.

Files selected for processing: 3

• AGENTS.md
• CONTRIBUTING.md
• docs/contributing.md

Files with no reviewable changes: 1

• CONTRIBUTING.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

Walkthrough

The AI contribution guidance now permits AI-assisted GitHub content when contributors review it before posting and disclose AI assistance. The changes replace prior restrictions on AI replies and remove a warning about bans across jdx projects.

Changes: AI contribution guidance

Layer / File(s)	Summary
Review and disclosure requirements AGENTS.md, docs/contributing.md, CONTRIBUTING.md	The guidance permits AI-assisted GitHub content after user review and requires disclosure. It removes prior reply eligibility rules, the ban warning, and the restriction on batch replies.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: greptile-apps

Merge Risk: Minimal · up to cea40

No actionable merge-blocking risk remains.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: removing the AI reply restriction from the contributing documentation.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[greptile-apps]

Confidence Score: 5/5

[Medium impact] This documentation-only PR appears safe to merge.

Summary

Removes AI reply restrictions from the three contributor guides while keeping human review and disclosure requirements.

• People can use AI to help write replies without contribution limits.

_{Reviews (1) · Last reviewed commit: "docs(contributing): remove the AI reply ..." · Reviewed by Greptile}

[github-actions]

Instruction counts

benchmark	trend	instructions	Δ	wall (min)	Δ
markdown	▁▁▇▆▆▆▆▆▆▆▇▆▆▆▆██▇▇	266,968,742 → 266,960,750	-0.00%	46.96 → 47.35ms	+0.84%
startup	▆▆█▆▆▆▆▆▆▆▆▆▆▆▆▆▆▁▇	1,010,474 → 1,017,369	+0.68%	1.33 → 1.38ms	+3.75%

No instruction-count regression above 1%.

_{Only instruction counts gate. Wall clock is shown for context — on identical hardware it moves 4-20% run to run.}

_{Measured by tak — instruction-counted CLI benchmarks, stored in this repository's git notes.}

Shadow comparison

Parsing mise use -g node@20 against a shadow of mise's committed spec.
Reported, not gated: the shadow grows as the derive learns to express more, so
what to watch is the ratio rather than either column.

framework	stripped binary, bytes
usage	1249944
bpaf	2494640
clap	3100904

framework	instructions, cold parse	vs usage
usage	8295	—
clap	6313736	761x
bpaf	21909300	2641x

                                              min       p01       p10    median
usage-rs: argv -> struct                      749       754       768       781  ns
clap: build tree + parse -> struct        1245955   1247754   1254226   1266046  ns
bpaf: build parser + parse -> struct      3435365   3435365   3456612   3493880  ns

usage: argv -> struct                             756 ns      0.76 µs
clap: build tree + parse -> struct            1264219 ns   1264.22 µs
clap: parse -> struct, tree reused              49965 ns     49.96 µs
clap: build tree only                          750115 ns    750.12 µs

_{cea400b5d622 vs b15054a4a6de · measured on the runner, not pushed to the history.}