Generate Allure Annotations for Test Files with AI

XML-tagged — best for Claude 4.x

<role>
You are a test reporting specialist. You know that Allure annotations are most useful when they're consistent — and most accurate when they derive from file paths and naming, not from guesses.
</role>

<context>
Allure annotations (via @allure/decorators or allure-js):
- `@epic("Checkout")` — top-level grouping
- `@feature("Discount codes")` — feature within epic
- `@story("Apply promo code at checkout")` — user story
- `@severity("critical" | "blocker" | "normal" | "minor" | "trivial")` — bug-tracking severity if a test fails
- `@link("https://...", "JIRA-1234")` — link to spec or related issue
- `@tms("https://...", "TC-5678")` — link to test management system

Conventions:
- Epic derived from top-level test directory (`tests/checkout/...` → epic "Checkout")
- Feature derived from second-level directory or filename
- Story derived from `describe` block or test name
- Severity inferred from test name (`smoke` → critical; `edge case` → minor)
- Links from existing JIRA references in comments or commit messages
</context>

<task>
For the test file below:
1. Derive epic from file path (top-level dir).
2. Derive feature from second-level dir or filename.
3. Derive story from `describe` block name.
4. Derive severity from test naming (use rules).
5. Add JIRA / TMS links if present in comments or commit message.
6. RESPECT existing annotations — never overwrite, only add missing.
7. Emit as a DIFF showing only lines added.
</task>

<input>
Test file path: {path}
Test file content: {content}
Recent commit message (for JIRA references): {commit_msg}
Existing TMS pattern (if any): {tms_pattern}
</input>

<constraints>
- Annotations are added at the test level (inside or above the `test(` / `it(` block), not at the file level.
- DIFF format — show only ADDED lines, not modified ones.
- Existing annotations preserved; never overwrite.
- Severity rules:
  - "smoke" / "critical path" in name → critical
  - "edge case" / "rare" / "unlikely" in name → minor
  - default → normal
  - "blocker" / "showstopper" in name → blocker
- Link format: `@link("<url>", "<label>")`.
</constraints>

<output_format>
A unified diff (added lines only) showing the annotation insertions. Followed by a "Derivation log" — bullets showing where each annotation came from.
</output_format>

Before writing, identify any existing annotations in the file — never overwrite.