メニュー
GitHub Actions workflows, testing automation, deployment triggers for CampusOS. Use when setting up CI/CD, automating tests, configuring deployments, or managing workflow triggers.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ci-cd-pipeline |
| description | GitHub Actions workflows, testing automation, deployment triggers for CampusOS. Use when setting up CI/CD, automating tests, configuring deployments, or managing workflow triggers. |
Create .github/workflows/ci.yml:
on:
push: { branches: [main] }
pull_request: { branches: [main] }
steps:
- uses: actions/checkout@v4
- uses: pnpm/action-setup@v2
- uses: actions/setup-node@v4
with:
node-version: 18
cache: 'pnpm'
- run: pnpm install --frozen-lockfile
- run: pnpm lint
- run: pnpm -C apps/vendor test -- --run
- run: pnpm -C apps/resource test -- --run
- run: pnpm -C apps/scheduling test -- --run
- run: pnpm -C apps/budget test -- --run
Note: CampusOS uses Vitest (not Jest). Each module has its own vitest.config.js.
- run: pnpm build # Backend build
- run: cd frontend && pnpm build # Frontend build (Next.js)
developmainenvironment: production for approval gates# Run the same checks CI runs
pnpm install --frozen-lockfile
pnpm lint
pnpm -C apps/vendor test -- --run
pnpm build
# Validate workflow syntax locally
act -j test_job
| Issue | Solution |
|---|---|
| pnpm cache not working | Use actions/setup-node@v4 with cache: 'pnpm' |
| Tests fail in CI, pass locally | Use --frozen-lockfile; check env vars |
| Node version mismatch | Pin to Node 18 in workflow |
Build React components in Next.js using CampusOS patterns. Use when implementing UI components, working with the App Router, styling with Tailwind CSS v4, or managing forms with react-hook-form and Zod.
Comprehensive frontend development hub — UI/UX design, React/Next.js patterns, Tailwind CSS v4, shadcn/ui components, Three.js 3D graphics, creative web experiences, data visualization, diagramming, Figma integration, accessibility, game development, scroll animations, and design systems. Use for ANY frontend task: building components, designing interfaces, styling, theming, animations, charts, responsive layouts, mobile design, or implementing design patterns.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
Generate commit titles and descriptions from uncommitted changes. Use when the user asks to generate a commit message, wants help writing a commit, or says 'commit', 'commit message', 'what should I commit', or similar.
Generate PR titles and descriptions from commit history. Use when the user asks to generate a PR description, wants help writing a pull request, provides commit titles/messages, or says 'PR', 'pull request', 'PR description', or similar.