{"owner":"allure-framework","repo":"allure2","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Project Guide\n\nUse [Allure Agent Mode](docs/allure-agent-mode.md) for all test-related work in this repository.\n\n- Read `docs/allure-agent-mode.md` before designing, writing, reviewing, validating, debugging, or enriching tests.\n- 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.\n- Use `allure agent` for smoke checks too, even when the change is small or mechanical.\n- Only skip agent mode when it is impossible or when you are debugging agent mode itself.\n- If agent-mode output is missing or incomplete, debug that first rather than silently falling back to console-only review.\n- Use Allure agent-mode when adding tests for features or fixes so expectations, evidence quality, and scope review are part of the loop.\n"},"files":{"AGENTS.md":"# Project Guide\n\nUse [Allure Agent Mode](docs/allure-agent-mode.md) for all test-related work in this repository.\n\n- Read `docs/allure-agent-mode.md` before designing, writing, reviewing, validating, debugging, or enriching tests.\n- 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.\n- Use `allure agent` for smoke checks too, even when the change is small or mechanical.\n- Only skip agent mode when it is impossible or when you are debugging agent mode itself.\n- If agent-mode output is missing or incomplete, debug that first rather than silently falling back to console-only review.\n- Use Allure agent-mode when adding tests for features or fixes so expectations, evidence quality, and scope review are part of the loop.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Project Guide\n\nUse [Allure Agent Mode](docs/allure-agent-mode.md) for all test-related work in this repository.\n\n- Read `docs/allure-agent-mode.md` before designing, writing, reviewing, validating, debugging, or enriching tests.\n- 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.\n- Use `allure agent` for smoke checks too, even when the change is small or mechanical.\n- Only skip agent mode when it is impossible or when you are debugging agent mode itself.\n- If agent-mode output is missing or incomplete, debug that first rather than silently falling back to console-only review.\n- Use Allure agent-mode when adding tests for features or fixes so expectations, evidence quality, and scope review are part of the loop.\n","category":"root","tokens":253}]}