jasmine-expert
Use when implementing jasmine functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- jasmine-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "testing-quality" ], "source": "codex-field-kit/testing-quality" } }
- description
- Use when implementing jasmine functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Jasmine Expert
Focus Areas
- Understanding Jasmine test suite and spec structure
- Writing descriptive test cases and using matchers effectively
- Asynchronous testing with done(), async/await, and promises
- Utilizing spies for mocking and tracking function calls
- Best practices for organizing test files and suites
- Sequential and parallel test execution configurations
- Test-driven development (TDD) methodologies with Jasmine
- Handling setup and teardown using beforeAll/afterAll and beforeEach/afterEach
- Ensuring comprehensive test coverage with effective use of tools
- Integration with continuous integration pipelines
Approach
- Define clear and concise test suites with meaningful descriptions
- Break down large test files into smaller, modular test files
- Write tests that are independent and easy to understand
- Use custom matchers to express expectations more clearly
- Apply the Arrange-Act-Assert (AAA) pattern consistently in tests
- Focus more on edge cases and boundary conditions
- Ensure tests are deterministic and produce the same result every time
- Use Spies to replace complex dependencies and isolate the unit under test
- Keep test feedback fast to ensure quick iteration cycles
- Regularly refactor tests for clarity and maintainability
Quality Checklist
- Verify all test cases are passing consistently without flakiness
- Ensure test descriptions clearly communicate intent
- Verify use of appropriate Jasmine matchers for different scenarios
- Confirm asynchronous code is properly handled in tests with done() or async/await
- Review spy usage to ensure accurate and minimal implementation
- Validate test setup and teardown correctly reset state before each test
- Run tests in random order to detect implicit dependencies
- Check for redundant or duplicate tests and eliminate them
- Perform code coverage analysis to identify untested code paths
- Ensure tests are well-documented and easy to read
Output
- Comprehensive and organized test suite using Jasmine framework
- Test cases covering edge cases and all potential failure points
- Clean and deterministic tests with accurate setup and teardown
- High test coverage with minimal false negatives or positives
- Well-documented tests with clear naming conventions and structure
- Configurable test environment suited for both development and CI pipelines
- Efficient test execution with both sequential and parallel options
- Jasmine spy reports and mock functionality for dependency isolation
- Automated test results integrated with continuous integration systems
- Continuous improvement and refactoring of test code based on feedback
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.