feat: incorporate the Drupal.org AI contribution policy into bundled skills - #375
Merged
Merged
Conversation
…skills Agents driving drupalorg produce code and text the user submits under Drupal.org's policy on the use of AI when contributing. The skills now carry that policy as operational checkpoints: read the thread before writing, keep diffs minimal and explainable, pass local checks and the MR pipeline before hand-off, never push to someone else's MR unannounced, draft the required AI-Generated disclosure, and hand summaries over as drafts in the user's own words. A shared checklist lives in references/ai-contribution-policy.md and is served by skill:get drupalorg-cli --full. The discovery stub, main skill, work-on-issue and issue-summary-update skills, workflow references, and README point to it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
4 tasks
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The bundled agent skills now carry Drupal.org's policy on the use of AI when contributing as operational checkpoints, so contributors using agents with this CLI adhere to it by default.
Why
Agents driving
drupalorgproduce code and text the user submits under their own account. The policy holds the human responsible for every line, forbids drive-by contributions, and requires disclosure of significant AI-generated work. Violations lead to account bans. None of that was represented in the skills.How
skill-data/drupalorg-cli/references/ai-contribution-policy.md, served byskill:get drupalorg-cli --full. It covers: read the thread first, minimal and explainable diffs, no unverified dependencies, green pipeline before hand-off, never push to someone else's MR unannounced, theAI-Generated: Yes (...)disclosure format, summaries in the user's own words, and staying responsive to feedback.drupalorg-cliskill and the installed discovery stub each gain a short "Contribution policy" section with the non-negotiables.drupalorg-work-on-issuegains[POLICY]checkpoints: fetch comments and report prior attempts in Step 1, stop when the MR author is not the user in Step 3, forbid out-of-scope refactors in the work loop, require a drafted disclosure before flipping to Needs review, and remind the user about follow-up.drupalorg-issue-summary-updaterefuses updates with no verified insight, hands over a draft to rewrite rather than paste, and adds a disclosure step.Known gap
--with-commentsis silently ignored for GitLab work items, so the skills tell agents to fall back toglab issue view --commentsfor those. Tracked in #374.Testing notes
vendor/bin/phpunit: 212 tests pass.php drupalorg skill:get drupalorg-cli --fullincludes the newai-contribution-policyreference.drupalorg skill:get drupalorg-cliholds.🤖 Generated with Claude Code