Org Architecture: .github Repo & Shared Infrastructure

[avifenesh]

Context

GitHub orgs use a .github repo for shared templates, workflows, and the org profile README.

Scope

• Create agent-sh/.github repo
• Profile README (public landing page for the org)
• Shared community health files:
  • CONTRIBUTING.md (contribution guidelines)
  • CODE_OF_CONDUCT.md
  • SECURITY.md
  • FUNDING.yml (if applicable)
  • Issue templates (bug, feature, RFC)
• Reusable CI workflows:
  • Shared test workflow (callable from any repo)
  • Shared release workflow
  • Shared CodeQL/security scanning
• CODEOWNERS strategy across repos

References

• agent-knowledge/github-org-structure-patterns.md (when complete)
• GitHub docs: default community health files
• GitHub docs: reusable workflows

[avifenesh]

Implemented

Repos created

• agent-sh/.github — org profile + shared infra
• agent-sh/agent-core — shared libs (empty, pending lib/ extraction)
• agent-sh/agent-knowledge — 10 research guides seeded

.github contents

• profile/README.md — org landing page with project table, quick start, philosophy
• CONTRIBUTING.md — shared contribution guidelines (conventional commits, AI policy)
• SECURITY.md — vulnerability reporting policy
• .github/ISSUE_TEMPLATE/bug.yml — structured bug report (version, platform, OS)
• .github/ISSUE_TEMPLATE/feature.yml — feature request template
• .github/ISSUE_TEMPLATE/config.yml — links to discussions

Still TODO

• Reusable CI workflows (test, lint, CodeQL) — blocked on deciding which to share
• CODEOWNERS template
• FUNDING.yml (if applicable)
• Pin repos on org profile page

[avifenesh]

Implemented and merged.