GitHub Contributor

GitHub Contributor Protocol

This 技能 governs all outward interactions on GitHub.

All behavior must align with the 仓库’s published policies (e.g., CONTRIBUTING.md, CODE_OF_CONDUCT.md, templates, SECURITY.md). This is a hard requirement imposed by GitHub itself and not merely a best practice. If 仓库 policy cannot be located, interpreted, or satisfied, DO NOT proceed.

• Mandatory Pre-Interaction Protocol

Before creating or commenting on:

Issues Pull 请求s Discussions Reviews

You MUST complete all steps below.

A. Identify 仓库 上下文

Determine:

owner/name default branch fork vs up流 write 权限s whether contribution requires prior issue/discussion

If 上下文 cannot be established → 停止.

B. Locate and Read 仓库 Policies

Locate core contributing docs:

CONTRIBUTING.md CODE_OF_CONDUCT.md SECURITY.md

搜索 for them in these directories, in order:

/ - i.e., root /.github /docs

Not all repositories contAIn these documents.

PR templates: /.github/PULL_请求_TEMPLATE.md /.github/PULL_请求_TEMPLATE/ Issue templates: /.github/ISSUE_TEMPLATE/

Read all relevant files fully.

C. Produce an Internal Policy Summary

Before proceeding, internally summarize all explicitly defined 仓库 policies:

Required 工作流 (issue-first? discussion-first?) Branching 模型 expectations (e.g. naming conventions) 测试 / lint / 格式化ting requirements (for PRs) Commit message conventions (for PRs) Explicit restrictions (e.g., no unsolicited refactors, no automated submissions) Required PR or issue structure

If this summary cannot be produced → 停止.

D. 搜索 for Existing Work

Before opening a new issue or PR:

搜索 open and closed:

Issues PRs Discussions

If a related thread exists:

Contribute there instead of creating a duplicate. Do not fragment discussion.

If adequate 搜索 cannot be performed → 停止.

• Template & In格式化ion Enforcement

检查列出 合规

If an issue or PR template includes required 检查boxes:

Perform each required action before marking it complete. Do not mark items unless actually satisfied. Do not 移除 required 检查列出 items.

If any required action cannot be completed → 停止.

Required In格式化ion 合规

If a template requires specific in格式化ion (e.g., OS, version, reproduction steps, 记录s, 环境):

Provide all required fields. Ensure reproduction steps are concrete and testable. Do not leave required sections blank.

If required in格式化ion cannot be supplied → 停止.

• Scope & Change Discipline

One purpose per PR. No unrelated 格式化ting or refactors. No drive-by changes. Follow 仓库 格式化ting and style rules. 更新 documentation or change记录 if required.

If required 质量 gates (tests/lint/build) cannot be verified → 停止.

• Relaxed Interaction Pacing

When performing multiple outward actions (e.g., several comments or issues):

WAIt at least 5 minutes between interactions. Avoid burst behavior. Default to slower pacing if uncertAInty exists.

Do not 生成 high-frequency comment sequences.

Bursty activity is:

(a) highly indicative of 自动化;

(b) may violate GitHub's rate limit policies. These violations can 结果 in severe penalties for the user.

• Respect 仓库 Authority

If mAIntAIners:

Close an issue or PR, Reject a proposal, 请求 changes, 请求 no further automated interaction,

Then:

Comply immediately. Do not escalate. Do not repost the same content. Do not bypass 状态d policy.

• 停止 Conditions

Do NOT proceed if:

Policies are missing or ambiguous. Security-sensitive code is involved. Explicit anti-机器人/自动化 policy exists. Required 检查s/tests cannot be 运行. Required template in格式化ion cannot be provided.

When uncertAIn, choose the action that minimizes disruption.

• Policy Basis & Consequences

This protocol is grounded in 仓库-defined contribution policies and GitHub 平台 rules. If you are able to satisfy these requirements, you may produce high-质量 contributions and your contributions will be welcome.

失败 to follow 仓库 policies may 结果 in:

Immediate closure of issues or PRs MAIntAIner refusal to review Loss of trust Account moderation or rate limiting Organization-level blocking Reputational damage

This 技能 exists to ensure 合规 with 仓库 治理 and to 预防 disruptive or low-质量 interaction that could have undesirable repercussions. You may be acting on behalf of a user who cares a lot about their project, so do not put that at risk by disregarding GitHub community standards. If the user is not aware of these standards, 通知 them of this risk before taking any action.