Open Brain · OB1

Contribution Pipeline

From first idea to community celebration — every step automated or guided, nothing falls through the cracks.

Contributor Journey

What happens when someone has an idea for Open Brain

1
Open an Issue Contributor
Pick from 8 issue templates — recipe submission, bug report, extension proposal, or free-form. Templates guide the contributor to provide exactly what reviewers need.
2
Claude Triages Automatically AI · Automated
Within 60 seconds, Claude classifies the issue (bug, recipe idea, schema, extension, question), checks for duplicates, assesses scope fit, suggests labels, and posts a welcoming comment with next steps.
claude-issue-triage.yml
3
Build the Contribution Contributor
Fork the repo, create a branch (contrib/username/feature), write the code. Every contribution gets its own folder with a README.md and metadata.json.
4
Open a Pull Request Contributor
Fill out the PR template — what it does, what it requires, confirmation of testing. The title follows [category] Short description format. Labels are applied automatically.
auto-label.yml
5
14 Mechanical Checks Run Automated
Folder structure, required files, metadata validation, credential scanning, SQL safety, category-specific artifacts, PR title format, binary blob detection, README completeness, primitive dependencies, scope isolation, link resolution, remote MCP pattern.
ob1-review.yml
6
Claude Reviews for Quality AI · Automated
Claude reads the full PR and evaluates 7 dimensions: alignment with OB1's mission, clarity of instructions, completeness, safety, unique value, design pattern compliance (remote MCP, RLS, JSONB metadata), and scope fit (flags contributions that should be standalone projects).
claude-review.yml
7
Admin Review Repo Manager
Repo manager runs /review-pr in Claude Code for the human-judgment layer — security deep scan (beyond CI's pattern matching), mission fit assessment, naming consistency, and PR quality. Generates a checklist, verdict, Discord draft, and post-merge tasks.
.claude/skills/review-pr.md
8
Merge Repo Manager
Admin approves and merges. Squash merge keeps the history clean. This triggers the next three automated steps.
9
Release Notes Drafted Automated
Every merge to main auto-updates a draft release in the Releases tab. Contributions are categorized (Recipes, Extensions, Schemas, etc.) using the labels already applied by auto-label. Contributors are credited automatically.
release-drafter.yml
10
Publish Release Repo Manager
When ready, the repo manager reviews the accumulated draft release notes and publishes. This can batch multiple merged contributions into one release.
11
Discord Announcement Automated
Publishing a release automatically posts a rich embed to the #show-and-tell Discord channel — with the release title, categorized changes, and contributor credits. No manual copy-paste needed.
discord-announce.yml
Human action
AI-powered (Claude)
Fully automated

Who Does What

Clear responsibilities for contributors and repo managers

Contributor

Anyone in the community
  • ▶ Open an issue describing the idea
  • ▶ Build the contribution in a fork
  • ▶ Open a PR with the template filled out
  • ▶ Address feedback from CI + reviewers
  • ▶ Celebrate in Discord when it ships

Repo Manager

Admin / maintainer
  • ▶ Review Claude's issue triage, adjust labels
  • ▶ Run /review-pr for security + mission fit
  • ▶ Approve, request changes, or reject
  • ▶ Merge when ready
  • ▶ Publish release notes periodically

Every PR Gets 21 Checks

14 mechanical rules + 7 AI judgment dimensions

Mechanical · 1
Folder Structure
Files only in allowed directories
Mechanical · 2
Required Files
README.md + metadata.json present
Mechanical · 3
Metadata Valid
All required fields, correct types
Mechanical · 4
No Credentials
Blocks API keys, tokens, connection strings
Mechanical · 5
SQL Safety
No DROP, TRUNCATE, or unqualified DELETE
Mechanical · 6
Category Artifacts
Right file types for the contribution type
Mechanical · 7
PR Title Format
[category] Short description
Mechanical · 8
No Binary Blobs
Max 1MB, no .exe/.dmg/.zip
Mechanical · 9
README Completeness
Prerequisites, steps, expected outcome
Mechanical · 10
Primitive Dependencies
Declared primitives exist and are linked
Mechanical · 11–14
Scope, Links, MCP Pattern
Changes within scope, links resolve, remote MCP only
AI · 1–7
Alignment, Clarity, Value, Design, Scope
Claude reviews what machines can't — judgment calls