Configure Allure Reporting

Overview

Use this skill when the primary goal is to make Allure reporting work in an existing project. Leave the project with the smallest idiomatic change that emits Allure results, generates or serves an Allure report, preserves or publishes CI artifacts, or adds the requested evidence integration, plus a clear validation summary.

If the goal is AI/coding-agent workflow guidance after reporting is configured, use allure-configure-agent-workflow. If the goal is writing, reviewing, debugging, or enriching tests through Allure agent mode, use allure-agent-mode.

Operating Style

Use the checklist as an advisory scaffold, not a rigid script.

• Prefer local project evidence over generic examples.
• Do additional local inspection or official documentation research when package names, config APIs, CI syntax, or installed CLI behavior may have changed.
• Treat package names, action versions, CLI flags, config keys, and environment variables as facts that need a source. Before introducing a new one, confirm it in project-local files, installed command help, official Allure/test-runner docs, or the package README/source.
• Keep optional surfaces out of scope unless the user asked for them, they are needed for validation, or the project already expects them.
• Do not claim setup works without either verified emitted Allure results or a clear caveat about what remains unverified.

Integration Surfaces