write-tests
Generate unit tests for existing code
Installation
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Voir la source ↗GuidesInstructions
Write Tests
Purpose
Generate unit tests for existing code
Routing
- Use when: Use when the user requests missing test coverage for a specific file or module.
- Do not use when: Don't use for snapshot tests or manual QA-only validation.
- Outputs: Prioritized test plan and test cases with clear coverage mapping.
- Success criteria: Includes positive/negative cases and test setup assumptions.
Trigger Examples
Positive
- Use the write-tests skill for this request.
- Help me with write tests.
- Use when the user requests missing test coverage for a specific file or module.
- Write Tests: provide an actionable result.
Negative
- Don't use for snapshot tests or manual QA-only validation.
- Do not use write-tests for unrelated requests.
- This request is outside write tests scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| path | string | Yes | Path to the file to test |
| framework | select | Yes | Testing framework to use |
Runtime Prompt
- Current runtime prompt length: 339 characters.
- Runtime prompt is defined directly in
../write-tests.json.
Exemples
Consultez les exemples du dépôt source.
Voir la source ↗Historique source
- Date d’indexation
- 2026-03-11
- Mise à jour de l’index
- 2026-03-11
- Branch
- main
Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!