good-oss-citizen

Scaffold the good-oss-citizen contribution gate into a consumer repository: a `pull_request_target` GitHub Actions check that fails any pull request whose description lacks a contribution declaration — an "AI Disclosure" section or an explicit "no AI assistance" statement — plus the vendored detection script, a PR template, and the tessl.json dependency entry. The gate enforces an outcome (AI use is disclosed) on the PR side, where it cannot be bypassed; it does not, and cannot, prove a tool ran. Use when a maintainer wants to add, install, set up, scaffold, enable, or wire up a contribution gate / a PR check that requires good-oss-citizen or AI-use disclosure before contributing.

Runs a structured 10-check pre-submission checklist against an open-source contribution before the contributor opens a pull request. Use when the user has written code for an open-source project and needs to prepare a PR, submit a contribution, or verify readiness. Triggers on "submit a PR", "open a pull request", "prepare the contribution", "ready to merge", "check my pull request". IMPORTANT — run this AFTER code is written but BEFORE submission. Checks: AI policy compliance and disclosure (including voluntary disclosure when no policy exists), diff size and focus, PR template, code style, commit conventions, tests, changelog and metadata, legal requirements (DCO/CLA), agent artifacts, slop detector patterns, and human ownership verification.

Analyzes project contribution guidelines, identifies the right venue (pull request, issue, discussion, RFC/KEP/DEP), checks issue metadata (claims, assignments, labels), searches for prior rejected attempts, and drafts proposals formatted to project templates. Use when the user wants to contribute to an open-source project, fix a bug, submit a PR, improve or refactor code, asks where to submit a change, or needs help choosing between PR/issue/discussion/RFC. Triggers on "fix this issue", "submit a PR", "refactor this", "improve this code", "open a pull request". IMPORTANT — run this AFTER recon and BEFORE writing code to verify the right venue and check for prior attempts.

Analyze an open source project's contribution norms, AI policy, conventions, and recent PR history before writing any code. Use when the user wants to contribute to an open source or GitHub project, fix a bug, submit a pull request, open a PR, make a contribution, or asks about contribution guidelines. Triggers on phrases like "fix this bug", "submit a PR", "contribute a fix", "open a pull request", "help me contribute", "how do I contribute", "what are the rules for this OSS project". IMPORTANT — run this BEFORE writing any code for an open source project.

Check an already-open issue or pull request body against the host repo templates and draft a suggested comment for human review, not posting. Use when asked to triage an existing issue/PR, decide whether an existing body is good enough before responding, review whether it follows the repo template, or draft a comment asking for missing information. Triggers include "triage this issue", "review this existing PR", "does this PR follow the template", "check whether the PR body follows the repository's pull request template", "check whether the issue body follows the repository's issue template", "quick check on this open issue", "body is good enough", "asked for anything more before I respond", and "what's missing from this PR body". For NEW issue/PR drafts use `propose`; for own PR pre-submission verification use `preflight`.