agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/github-contribution-governance/SKILL.md

github-contribution-governance

Skill40 starsChanged 3 days agoApache-2.0View on GitHub

Use when verifying GitHub contribution attribution, green-dot eligibility, commit author email, PR targeting, and merge readiness for Hussh work so daily contributions land on the intended GitHub profile.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Avoid overlap with repo-context, github:yeet, and github:gh-fix-ci.

    line 12
  2. Distinctive:

    Do not rewrite pushed history without explicit branch-level user approval.

    line 38
  3. Distinctive:

    Do not merge before required checks and repo policy are understood.

    line 39
  4. Distinctive:

    Do not expose private verified emails.

    line 40
  5. Very specific:

    Do not handle failing CI root cause.

    line 41
  6. Distinctive:

    If local commit email is blank, generic, or not associated with the account, set repo-local Git config before committing.

    line 52
  7. Distinctive:

    Before committing, confirm worktree scope and stage only files that belong to the contribution task.

    line 53
  8. Distinctive:

    After committing and pushing, verify attribution on the pushed commit through GitHub.

    line 54
  9. Distinctive:

    If there is no PR, create one against the requested base or repository default branch.

    line 55
  10. Very specific:

    Do not stop at branch push for green-dot credit.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub Contribution Governance

Purpose and Trigger

  • Primary scope: github-contribution-governance
  • Trigger on GitHub contribution graph, green-dot, commit attribution, author-email, PR target, or merge-readiness questions for Hussh work.
  • Avoid overlap with repo-context, github:yeet, and github:gh-fix-ci.

Coverage and Ownership

  • Role: spoke
  • Owner family: repo-operations

Owned repo surfaces:

  1. .agents/skills/github-contribution-governance
  2. .agents/workflows/github-contribution-governance

Non-owned surfaces:

  1. repo-operations
  2. .github/workflows
  3. docs

Do Use

  1. Confirm active GitHub account and local Git author identity before commits.
  2. Diagnose missing contribution graph, green-dot, PR target, or attribution behavior.
  3. Build maintainer-harvest attribution plans that separate GitHub commit credit, public acknowledgement, and internal impact credit.

Do Not Use

  1. Do not rewrite pushed history without explicit branch-level user approval.
  2. Do not merge before required checks and repo policy are understood.
  3. Do not expose private verified emails.
  4. Do not handle failing CI root cause; route to github:gh-fix-ci or repo-operations.

Read First

  1. docs/operations/releases/ci.md
  2. docs/operations/releases/branch-governance.md
  3. .agents/skills/github-contribution-governance/references/contribution-attribution.md

Workflow

  1. Establish active GitHub login and repo-local Git author identity.
  2. If local commit email is blank, generic, or not associated with the account, set repo-local Git config before committing.
  3. Before committing, confirm worktree scope and stage only files that belong to the contribution task.
  4. After committing and pushing, verify attribution on the pushed commit through GitHub.
  5. If there is no PR, create one against the requested base or repository default branch.
  6. Do not stop at branch push for green-dot credit; use the contribution rules in contribution-attribution.md.
  7. Monitor PR checks before merge and hand off failing CI to the CI owner.
  8. For maintainer harvests, decide co-author trailers versus acknowledgement before the commit lands.

Handoff Rules

  1. Broad or ambiguous repo workflow routes back to repo-operations.
  2. Full branch publish or PR creation can use github:yeet after identity is verified.
  3. Failing PR checks route to github:gh-fix-ci.
  4. Branch protection, merge queue, or deploy gates route to repo-operations.

Required Checks

gh auth status
gh api user --jq '.login'
git config --get user.email
python3 .agents/skills/codex-skill-authoring/scripts/skill_lint.py

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.