self-test
Pattern for testing your own code during implementation. Ensures quality before declaring complete.
Best use case
self-test is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Pattern for testing your own code during implementation. Ensures quality before declaring complete.
Pattern for testing your own code during implementation. Ensures quality before declaring complete.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "self-test" skill to help with this workflow task. Context: Pattern for testing your own code during implementation. Ensures quality before declaring complete.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/self-test/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How self-test Compares
| Feature / Agent | self-test | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Pattern for testing your own code during implementation. Ensures quality before declaring complete.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Self-Test Skill
Pattern for iterative testing during implementation.
## When to Load This Skill
- You are implementing code
- You need to verify your work before completing
- You want to catch issues early
## Self-Test Loop
```
WHILE implementation not complete:
Write/modify code
↓
Write tests for new code
↓
Run tests
↓
FAIL? → Fix code, retry
↓
Run lint
↓
FAIL? → Fix issues, retry
↓
Run typecheck
↓
FAIL? → Fix types, retry
↓
Continue to next piece
```
## Running Tests
Use project-specific test commands:
@.claude/skills/project/run-tests/SKILL.md
Common patterns:
```bash
# Run specific test file
npm test -- --testPathPattern={file}
pytest {file} -v
# Run affected tests
npm test -- --changedSince=HEAD
```
## Running Lint/Typecheck
Use project-specific commands:
@.claude/skills/project/lint/SKILL.md
Common patterns:
```bash
# TypeScript
npx tsc --noEmit
npx eslint {files} --fix
# Python
mypy {files}
ruff check {files} --fix
```
## Before Declaring Pre-Complete
Checklist:
- [ ] New code has tests
- [ ] All tests pass
- [ ] Lint passes
- [ ] Typecheck passes
- [ ] No console errors/warnings
If ANY fails, status is NOT `pre_complete`.
## Principles
- **Test as you go** - Don't batch at the end
- **Fix immediately** - Don't accumulate failures
- **Be honest** - Report actual statusRelated Skills
testing-strategies
Design comprehensive testing strategies for software quality assurance. Use when planning test coverage, implementing test pyramids, or setting up testing infrastructure. Handles unit testing, integration testing, E2E testing, TDD, and testing best practices.
backend-testing
Write comprehensive backend tests including unit tests, integration tests, and API tests. Use when testing REST APIs, database operations, authentication flows, or business logic. Handles Jest, Pytest, Mocha, testing strategies, mocking, and test coverage.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
game-test-case-generator
基于需求文档（xls/csv）生成专业游戏测试用例，支持完整用例和快速测试点两种模式。当用户提到"游戏测试"、"测试用例生成"、"需求转测试用例"、上传需求文档或原型时使用此技能。
wordpress-penetration-testing
This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugins", "exploit WordPress vulnerabilities", or "use WPScan". It provides comprehensive WordPress security assessment methodologies.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
web-security-testing
Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.
unit-testing-test-generate
Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
testing-qa
Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.
test-fixing
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
test-automator
Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.