Allure Test Agent Setup

Use this skill when a project wants to adopt Allure test-agent guidance for test work and test reviews.

If a command executes tests and its result will be used for smoke checking, reasoning, review, coverage analysis, debugging, or any user-facing conclusion, run it through allure agent. It preserves the original console logs and adds agent-mode artifacts without inheriting the normal report or export plugins from the project config.
Use allure agent for smoke checks too, even when the change is small or mechanical.
Only skip agent mode when it is impossible or when you are debugging agent mode itself.

Goal

Leave the project with:

root agent entry-file router guidance, such as AGENTS.md, CLAUDE.md, or other project-specific agent instruction files, that points test work to docs/allure-test-agent.md
a project docs/allure-test-agent.md guide with local wrappers, capabilities, Allure integrations, test-design conventions, run profiles, expectation controls, output/state policy, execution-signal notes, metadata conventions, and evidence conventions
enough Allure bootstrap guidance for the agent to continue, even if the project is not fully configured yet