skills.rest
Birdhouse-Labs
Birdhouse-LabsOFFICIAL
Explore all skills by this author →
Website𝕏@birdhouselabsaiGitHub

ci-checks

Runs Birdhouse CI checks locally across frontend, server, and plugin projects.

36|5|Updated Feb 27, 2026
Search Tags:#testing#github actions#bun#lint#ci#build verification#typecheck
One-click install
npx skills add https://github.com/Birdhouse-Labs/birdhouse --skill ci-checks-birdhouse-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-checks
Source: https://github.com/Birdhouse-Labs/birdhouse/tree/main/.agents/skills/internal/birdhouse-development/ci-checks
Command: npx skills add https://github.com/Birdhouse-Labs/birdhouse --skill ci-checks-birdhouse-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that local changes will pass GitHub Actions before merging requires knowing and running many separate checks across multiple projects. This Skill lists every Birdhouse CI check and the exact commands to run them locally, so failures are caught before pushing. ## Core Features & Use Cases - Frontend checks: Runs typecheck, lint, CSS lint, tests, and theme generation/validation plus build from projects/birdhouse/frontend. - Server checks: Runs typecheck, lint, tests, and build from projects/birdhouse/server. - Plugin checks: Runs typecheck, tests, and build from projects/birdhouse-oc-plugin. - Use Case: Before merging a feature branch, run each check as a separate tool call to isolate failures and confirm the branch is clean for GitHub Actions. ## Quick Start Run all Birdhouse CI checks locally for my current branch and tell me which ones fail.

Frequently Asked Questions about ci-checks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Birdhouse CI checks locally before merging?▼

Run each check as a separate tool call from the appropriate working directory: bun run typecheck, lint, lint:css, test, and theme validation plus build for the frontend; typecheck, lint, test, and build for the server; and typecheck, test, and build for the plugin.

What commands verify the Birdhouse frontend passes CI?▼

From projects/birdhouse/frontend run bun run typecheck, bun run lint, bun run lint:css, bun run test, then bun run generate:themes, bun run validate:themes, and bun run build. All must pass before merging.

How do I run CI checks inside a git worktree?▼

Prefix each project path with the worktree root, for example worktrees/my-feature/projects/birdhouse/frontend, then run the same bun commands from that directory.

Why do Birdhouse frontend tests fail when my changes are unrelated?▼

Frontend test failures may include pre-existing failures unrelated to your changes. Check whether the failing test files are ones you actually touched before investigating further.

Why run each CI check as a separate tool call?▼

Running each command separately isolates failures so the exact failing check is easy to identify, rather than digging through combined output from a single chained command.

Related Skills

Explore More Software Engineering Skills→
VIPER-MetricsVIPER-Metrics
1

implement-feature

Implement approved feature plans using git worktrees and phased execution.

Official
Advanced
519lab519lab
2

github-pr-workflow

Automate GitHub Pull Request lifecycle with branch creation, CI monitoring, and merging.

Official
Intermediate
DataDogDataDog
648

lint

Run Hatch-based lint, format, and quality checks on modified files.

Official
Advanced
SocketDevSocketDev
125

greening-ci-local

Run GitHub Actions workflows locally in Docker and retry paused steps.

Official
Intermediate