菜单
Oak's git conventions including branch naming (feat/fix/chore prefixes), commit messages (conventional commits format), PR creation with templates, code review process, and CI check monitoring. Use when working with git, creating branches, committing code, or managing pull requests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run the agentic scoring harness after changing agent prompts or execution code. Generates a scoring report that must be committed alongside code changes. Use after editing files in packages/aila/src/lib/agentic-system/agents/ or execution/.
Oak AI project TypeScript coding conventions including naming patterns (kebab-case files, PascalCase components, camelCase functions), component structure, error handling with cause, state management patterns, and tRPC implementation. Use when writing, reviewing, or refactoring code.
Development server and build commands for Oak AI project including running dev server on port 2525, production and development builds, and running scripts with environment variables. Use when starting local development, building the project, or running scripts.
Query and manage Oak AI squad tasks and sprints in Notion. Use when checking current sprint, finding tasks by status, updating task information, or understanding team priorities and workload.
Testing commands and patterns for Oak AI project including running Jest unit tests, E2E tests with Playwright, coverage reports, and filtering tests. Use when writing tests, running test suites, or debugging test failures.
| name | git-workflow |
| description | Oak's git conventions including branch naming (feat/fix/chore prefixes), commit messages (conventional commits format), PR creation with templates, code review process, and CI check monitoring. Use when working with git, creating branches, committing code, or managing pull requests. |
feat/AI-XXXX-description or feat/description (prefer ticket ID when available)fix/descriptionchore/description (for project/config changes)dev/descriptiontest/descriptionspike/descriptionrefactor/descriptiontype: description (conventional commits)feat:, fix:, docs:, style:, refactor:, perf:, test:, build:, ci:, chore:, revert:feat: add new lesson planner featurefix: resolve authentication bugdocs: update API documentationBefore committing or creating a PR, verify all quality checks pass:
pnpm prettier --write <changed-files>
# Or check all: pnpm prettier --check .
pnpm lint
# Or with auto-fix: pnpm lint:fix
pnpm type-check
# Or: pnpm check
# Run all tests
pnpm test
# Run specific test
pnpm test -- -t "test name pattern"
# Run E2E tests (if relevant)
pnpm test-e2e
.github/pull_request_template.mdpnpm prettier --check . before submittinggh pr edit <PR-number> --add-reviewer oaknational/ai-devsgh pr edit <PR-number> --add-reviewer usernameUse the check-prs script to monitor CI status across PRs:
# Check specific PRs
./scripts/check-prs.sh 940 941 942
# Check all your open PRs
./scripts/check-prs.sh
To wait for a specific check to complete:
PR=733; CHECK_NAME="lint"; TIMEOUT=120; INTERVAL=10; \
end=$(($(date +%s) + TIMEOUT)); \
echo "Polling PR #$PR for '$CHECK_NAME' (timeout: ${TIMEOUT}s)..."; \
while [ $(date +%s) -lt $end ]; do \
check_status=$(gh pr checks "$PR" | grep "^$CHECK_NAME" | awk '{print $2}'); \
echo "$(date '+%H:%M:%S') - $CHECK_NAME: ${check_status:-not found}"; \
[ "$check_status" != "pending" ] && echo "✓ Completed: $check_status" && break; \
sleep $INTERVAL; \
done || echo "⏱️ Timeout reached"
Common checks: lint, test-e2e, test-jest, sonarcloud, Vercel