Skip to content

aktonay/skillz / skills/development/test

Generate comprehensive tests for code and features. Use when writing new tests or improving test coverage for a behavior, bug fix, or regression.

Write Tests

When writing tests, follow these guidelines:

  1. Cover the happy path first.
  2. Cover edge cases, including empty inputs and boundary values.
  3. Cover error paths.
  4. Use one assertion per test where possible.
  5. Prefer descriptive test names.
  6. Test behavior, not implementation details.
  7. Use realistic test data.
  8. Mock external dependencies like network, database, and filesystem.

Preferred test structure:

describe('<ComponentOrFunction>', () => {
  it('<expected behaviour> when <condition>', () => {
    // Arrange
    // Act
    // Assert
  })
})

Aim for at least 1 happy path, 2 edge cases, and 1 error case per function.

finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 318kUpdated Claude CodeCodexUnverifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 318kUpdated Claude CodeCodexUnverifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 318kUpdated Claude CodeCodexUnverifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall