원클릭으로
run-tests
Run Jest tests for EduHub. Use when the user asks to run tests, execute test suite, check test coverage, or verify code changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Run Jest tests for EduHub. Use when the user asks to run tests, execute test suite, check test coverage, or verify code changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | run-tests |
| description | Run Jest tests for EduHub. Use when the user asks to run tests, execute test suite, check test coverage, or verify code changes. |
# From frontend-nx directory
cd frontend-nx
# Run all tests for edu-hub
yarn test
# Run tests in watch mode
yarn test --watch
# Run specific test file
yarn test --testPathPattern="MyComponent.test"
# Run with coverage
yarn test --coverage
*.test.ts or *.test.tsx__tests__/ folder# Tests matching a pattern
yarn test --testPathPattern="TableGrid"
# Single test file
yarn test --testPathPattern="components/common/TableGrid/TableGrid.test.tsx"
# Verbose output
yarn test --verbose
# Run only failed tests
yarn test --onlyFailures
Work with Pencil .pen design files via the Pencil MCP (batch_design, variables, guidelines). Use when creating or editing .pen files, exploring UI layouts in Pencil, generating wireframes for EduHub, or when the user mentions Pencil, .pen, or the highagency Pencil extension.
Inspect UI via cursor-ide-browser (Cursor Browser tab); fall back to user-playwright if internal browser MCP is unavailable. Use for @Browser, open tab, layout checks, localhost — or when user explicitly asks for Playwright.
Use this skill to generate well-branded interfaces and assets for EduHub by opencampus.sh, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
Draft and review EduHub commit messages using the repository's conventional-commit and semantic-release workflow. Use when writing commit messages, choosing feat vs fix vs chore, deciding whether a body is needed, preparing merge commit messages, or explaining release impact.
Create a GitHub issue on eduhub-org/eduhub and add it to the "EduHub Development" project board with a chosen Status (Backlog / Todo / In Progress / Done). Use when the user asks to "create an issue", "file a ticket", "add to backlog", or otherwise wants a new issue tracked on the project board.
Create and review EduHub Hasura schema migrations. Use when adding tables, columns, constraints, relationships, or other database schema changes, and when coordinating the required metadata, query, type-generation, and function follow-up steps.