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.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
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
- Very specific: line 12
Avoid overlap with repo-context, github:yeet, and github:gh-fix-ci.
- Distinctive: line 38
Do not rewrite pushed history without explicit branch-level user approval.
- Distinctive: line 39
Do not merge before required checks and repo policy are understood.
- Distinctive: line 40
Do not expose private verified emails.
- Very specific: line 41
Do not handle failing CI root cause.
- Distinctive: line 52
If local commit email is blank, generic, or not associated with the account, set repo-local Git config before committing.
- Distinctive: line 53
Before committing, confirm worktree scope and stage only files that belong to the contribution task.
- Distinctive: line 54
After committing and pushing, verify attribution on the pushed commit through GitHub.
- Distinctive: line 55
If there is no PR, create one against the requested base or repository default branch.
- Very specific: line 56
Do not stop at branch push for green-dot credit.
≈ “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.
Files
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, andgithub:gh-fix-ci.
Coverage and Ownership
- Role:
spoke - Owner family:
repo-operations
Owned repo surfaces:
.agents/skills/github-contribution-governance.agents/workflows/github-contribution-governance
Non-owned surfaces:
repo-operations.github/workflowsdocs
Do Use
- Confirm active GitHub account and local Git author identity before commits.
- Diagnose missing contribution graph, green-dot, PR target, or attribution behavior.
- Build maintainer-harvest attribution plans that separate GitHub commit credit, public acknowledgement, and internal impact credit.
Do Not Use
- Do not rewrite pushed history without explicit branch-level user approval.
- Do not merge before required checks and repo policy are understood.
- Do not expose private verified emails.
- Do not handle failing CI root cause; route to
github:gh-fix-ciorrepo-operations.
Read First
docs/operations/releases/ci.mddocs/operations/releases/branch-governance.md.agents/skills/github-contribution-governance/references/contribution-attribution.md
Workflow
- Establish active GitHub login and repo-local Git author identity.
- If local commit email is blank, generic, or not associated with the account, set repo-local Git config before committing.
- Before committing, confirm worktree scope and stage only files that belong to the contribution task.
- After committing and pushing, verify attribution on the pushed commit through GitHub.
- If there is no PR, create one against the requested base or repository default branch.
- Do not stop at branch push for green-dot credit; use the contribution rules in
contribution-attribution.md. - Monitor PR checks before merge and hand off failing CI to the CI owner.
- For maintainer harvests, decide co-author trailers versus acknowledgement before the commit lands.
Handoff Rules
- Broad or ambiguous repo workflow routes back to
repo-operations. - Full branch publish or PR creation can use
github:yeetafter identity is verified. - Failing PR checks route to
github:gh-fix-ci. - 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.pyDoes 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
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.

