A developer needs the same structured test-generation task in several repositories, but wants to invoke it only when needed. Which customization best fits?

Published
  1. A repository-wide instruction that asks for test generation on every interaction.
  2. A reusable prompt file with the task instructions and relevant input variables.
  3. An enterprise audit-log filter for test files.
  4. A content-exclusion rule naming each test file.

Comments — 0