AGENT SKILL

ava-expert

Use when implementing ava functionality with production-grade patterns and safeguards.

License 许可
MIT
最近更新
2026-04-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
ava-expert
metadata
{ "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
description
Use when implementing ava functionality with production-grade patterns and safeguards.

03 SKILL.md 正文

Ava Expert

Focus Areas

  • Understanding Ava's test execution model
  • Mastering Ava CLI arguments and options
  • Writing concise and effective test cases
  • Leveraging Ava's concurrent test execution
  • Implementing test hooks effectively
  • Utilizing assertions available in Ava
  • Structuring tests for readability and maintenance
  • Debugging test failures in Ava
  • Managing asynchronous tests with Ava
  • Enhancing performance of Ava test suites

Approach

  • Start each test file with clear setup and teardown
  • Use descriptive names for test cases
  • Ensure tests are independent and isolated
  • Take advantage of Ava's concurrent execution by default
  • Apply before and after hooks wisely to manage resources
  • Use only the necessary assertions in each test
  • Keep tests small and focused on a single behavior
  • Avoid stateful tests to prevent side effects
  • Refactor common setup code among tests
  • Embrace Ava's minimal syntax for clarity

Quality Checklist

  • Tests are clean and adhere to Ava's syntax
  • Each test case verifies a single unit of behavior
  • Utilize Ava's power-assert for detailed assertions
  • Async code is handled using async/await correctly
  • Global variables are avoided within tests
  • Execution times of test suites are optimized
  • Errors and warnings in console are addressed
  • DRY principle applied across test files
  • Constant test suite runtime across environments
  • Comprehensive code coverage with Ava's built-in support

Output

  • Well-documented test files with clear intentions
  • Efficient test execution leveraging Ava's concurrency
  • Error messages with detailed and actionable information
  • Consistent and reproducible test results
  • Codebase with >85% test coverage
  • Collection of tests that are quick to execute and diagnose
  • Report of potential performance bottlenecks in tests
  • Setup for continuous integration with Ava
  • Test automation scripts using Ava CLI
  • Guidance on best practices and test strategies using Ava

04 同仓库更多 Skills

0xharryriddle
0xharryriddle/codex-field-kit

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.

前端开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

swarm-planner

[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

super-swarm-spark

Only to be triggered by explicit super-swarm-spark commands.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

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).

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

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

Skill与智能体开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

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.

★ 3