Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

test-strategy-and-generation

Étoiles21

Forks2

Mis à jour10 juin 2026 à 17:57

Design the smallest effective set of tests for a change, then generate them in the project's style. Use when: fixing bugs, adding features, preventing regressions, or improving weak test coverage across web, JVM, Python, and native codebases.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Kory111111111111111111

Kory111111111111111111/yt-dlp-for-ableton

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	test-strategy-and-generation
description	Design the smallest effective set of tests for a change, then generate them in the project's style. Use when: fixing bugs, adding features, preventing regressions, or improving weak test coverage across web, JVM, Python, and native codebases.
argument-hint	Describe the change, bug, or code path that needs test coverage
user-invocable	true
disable-model-invocation	false

Test Strategy and Generation

When to Use

A bug fix needs a regression test
A new feature needs coverage before or after implementation
Existing tests are weak, noisy, or brittle
You need to choose between unit, integration, component, or end-to-end coverage
A change affects multiple languages or layers and the right test boundary is unclear

Approach

Good testing is selective. Do not maximize test count. Choose the smallest set of tests that proves the behavior, guards the highest-risk paths, and matches the codebase's testing style.

Prefer stable tests around contracts and behavior over tests that mirror implementation details.

Procedure

Identify the behavior that changed and the most valuable boundary to test.
Choose the lowest-cost test level that still provides confidence.
Enumerate happy path, edge, failure, and regression cases.
Generate tests in the repo's style.
Validate that the tests are deterministic and would fail for the broken behavior.

Use workflow.md for the full test-selection flow and stack-specific guidance.

Output

Deliver:

Recommended test levels
Specific cases to cover
Generated tests or test skeletons in project style
Gaps that still require manual or exploratory testing

Example Usage Prompts

/test-strategy-and-generation -> "Add regression tests for this pagination bug"
/test-strategy-and-generation -> "What tests should back this new Spring service flow?"
/test-strategy-and-generation -> "Generate the right pytest coverage for this upload endpoint"

Examples

See EXAMPLES.md for example test-boundary choices, case selection, and output formats.

References

../../copilot-instructions.md - Shared validation, edge-case, and codebase-pattern rules
workflow.md - Detailed test-selection flow and stack-specific guidance

Plus depuis ce dépôt

même dépôt

agent-code-deslop

Kory111111111111111111/yt-dlp-for-ableton

Clean up AI-generated or over-engineered code while preserving behavior. Use when: refactoring noisy code, removing dead code, simplifying abstractions, or making code more idiomatic without changing the public API.

2026-06-1021

code-change-review

Kory111111111111111111/yt-dlp-for-ableton

Review AI-generated code changes for unintended consequences, logic errors, UI inconsistencies, and context-specific issues. Use when: code has just been modified, flag potential bugs, verify UI consistency, check implementation correctness against project patterns.

2026-06-1021

feature-implementation-planner

Kory111111111111111111/yt-dlp-for-ableton

Turn a feature request, issue, or rough spec into a safe implementation plan for an existing codebase. Use when: planning a new feature, scoping impacted files, evaluating trade-offs, or deciding rollout steps before coding.

2026-06-1021

idea-to-project

Kory111111111111111111/yt-dlp-for-ableton

Turn small ideas into fully-fledged projects through structured discovery, research, and specification. Use when: starting a new project from a rough idea, need to validate feasibility, want to create comprehensive project documentation, exploring feature requirements and design patterns. Conversational, adaptive workflow.

2026-06-1021

impl-quality-audit

Kory111111111111111111/yt-dlp-for-ableton

Audit the quality and robustness of an implementation by inventorying the code, understanding how it works, then researching reference examples and community standards online to identify gaps. Use when: checking if a DSP routine is correct, validating a JUCE component follows best practices, reviewing an entire module for structural weaknesses, or verifying a feature is not just "working" but properly implemented.

2026-06-1021

init-ralph

Kory111111111111111111/yt-dlp-for-ableton

Initialize or bootstrap a Ralph workspace. Use when starting a repo, preparing the workspace for first use, creating or seeding the `.ralph` folder, filling the first project understanding / journal entries, and documenting setup blockers before substantive work begins.

2026-06-1021

name	test-strategy-and-generation
description	Design the smallest effective set of tests for a change, then generate them in the project's style. Use when: fixing bugs, adding features, preventing regressions, or improving weak test coverage across web, JVM, Python, and native codebases.
argument-hint	Describe the change, bug, or code path that needs test coverage
user-invocable	true
disable-model-invocation	false

Test Strategy and Generation

When to Use

A bug fix needs a regression test
A new feature needs coverage before or after implementation
Existing tests are weak, noisy, or brittle
You need to choose between unit, integration, component, or end-to-end coverage
A change affects multiple languages or layers and the right test boundary is unclear

Approach

Good testing is selective. Do not maximize test count. Choose the smallest set of tests that proves the behavior, guards the highest-risk paths, and matches the codebase's testing style.

Prefer stable tests around contracts and behavior over tests that mirror implementation details.

Procedure

Identify the behavior that changed and the most valuable boundary to test.
Choose the lowest-cost test level that still provides confidence.
Enumerate happy path, edge, failure, and regression cases.
Generate tests in the repo's style.
Validate that the tests are deterministic and would fail for the broken behavior.

Use workflow.md for the full test-selection flow and stack-specific guidance.

Output

Deliver:

Recommended test levels
Specific cases to cover
Generated tests or test skeletons in project style
Gaps that still require manual or exploratory testing

Example Usage Prompts

/test-strategy-and-generation -> "Add regression tests for this pagination bug"
/test-strategy-and-generation -> "What tests should back this new Spring service flow?"
/test-strategy-and-generation -> "Generate the right pytest coverage for this upload endpoint"

Examples

See EXAMPLES.md for example test-boundary choices, case selection, and output formats.

References

../../copilot-instructions.md - Shared validation, edge-case, and codebase-pattern rules
workflow.md - Detailed test-selection flow and stack-specific guidance