Skip to content

CI: lint the brain with the gbrain-company-brain action - #9

Merged
mattzimak merged 2 commits into
mainfrom
ci/brain-lint-action
Sep 21, 2026
Merged

mattzimak merged 2 commits into
mainfrom
ci/brain-lint-action

Conversation

@mattzimak

Copy link
Copy Markdown
Member

Feature

Every pull request to this template now runs the company-brain linter from gbrain-company-brain v0.2.0. A page in the wrong folder, a type the schema pack does not declare, an undated decision or a wikilink gbrain would drop shows up as an annotation on the file that broke it. Repositories created from this template inherit the check.

Workflow

New job brain-lint ("Company brain lint") in .github/workflows/validate.yml, next to frontmatter, secrets and links. Errors fail the job; warnings annotate without failing.

Technical

  • uses: mattzimak/gbrain-company-brain@v0.2.0 with path: . (composite action: setup-bun, then lint --format github).
  • No secrets or permissions beyond contents: read.
  • Verified locally on main before opening: 7 pages, 0 errors, 1 warnings (FACTSHEET.md has no frontmatter, which is by design and only a warning).

🤖 Generated with Claude Code

mattzimak and others added 2 commits September 21, 2026 02:56
Adds a fourth check, 'Company brain lint', that runs
mattzimak/gbrain-company-brain@v0.2.0 on the repository root. It applies the
same rules the skillpack runs before a gbrain sync and annotates the pull
request on the file that broke. Local run on main: 7 pages, 0 errors, 1 warning
(FACTSHEET.md has no frontmatter, by design).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The new brain lint job flagged it: without frontmatter gbrain syncs the
runbook as an untyped page. gbrain's skillpack doctor only requires the file
to be non-empty and prints it as is, so frontmatter is safe there.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@mattzimak
mattzimak merged commit 86ab553 into main Sep 21, 2026
5 checks passed
@mattzimak
mattzimak deleted the ci/brain-lint-action branch September 21, 2026 00:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant