Generate Allure Report
SkillProductivityRuns a generate Claude Skill script that turns project YAML metadata into Allure test reports.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Generate Allure Report skill
About this skill
Generate Allure-ready reports from bigpowers YAML metadata. Reads execution-status.yaml, release-plan.yaml, epic capsules, task YAMLs, cycle-times.yaml, and bug registry to produce allure-results/junit-results.xml, categories.json, and executor.json. Use when preparing progress dashboards, integrati
What this skill tells your AI
The instructions your AI receives, as published by danielvm-git/bigpowers in skills/generate-allure-report/SKILL.md and read by ahel’s review.
Generate Allure TestOps-compatible reports from bigpowers project metadata. Produces JUnit XML for story-level test results, custom categories for filtering, and executor metadata — all in the allure-results/ directory.
Quick Start
bash scripts/generate-allure-report.sh
What It Produces
Three files in allure-results/:
| File | Description |
|---|---|
junit-results.xml | One <testcase> per story with <properties> for risk, security, WSJF, tier, wave, and status. Incomplete stories get a <failure> element. |
categories.json | Custom Allure categories for filtering by epic, risk level (P0), and security reviews. |
executor.json | Build metadata — name, type, version from release-plan.yaml, build order. |
Data Sources
See REFERENCE.md
Verify
test -f allure-results/junit-results.xml && test -f allure-results/categories.json && test -f allure-results/executor.json
Handoff
- next_skill: null (terminal skill — no downstream workflow step)
Signals
- GitHub stars
- 248
- Forks
- 19
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
generate-allure-report- Source
- github.com/danielvm-git/bigpowers