daily-testing-workflow
Use this skill when you need a day-by-day QA routine including planning, execution, bug reporting, and end-of-day wrap-up; triggers include daily testing workflow and daily QA routine.
Best use case
daily-testing-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when you need a day-by-day QA routine including planning, execution, bug reporting, and end-of-day wrap-up; triggers include daily testing workflow and daily QA routine.
Teams using daily-testing-workflow should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/daily-testing-workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How daily-testing-workflow Compares
| Feature / Agent | daily-testing-workflow | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill when you need a day-by-day QA routine including planning, execution, bug reporting, and end-of-day wrap-up; triggers include daily testing workflow and daily QA routine.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Daily Testing Workflow **中文版：** 见对应中文技能。 ## When to Use - Need a structured daily testing workflow flow instead of a single testing task. - Need to move step by step across a testing phase with the matching prompts. ## Output Format Options Markdown by default unless the request explicitly asks for another format. ## How to Use 1. Check [reference.md](reference.md) first and find the prompt file for the current step. 2. Open the matching file under `prompts/` and add only the context that matters: scope, environment, risks, constraints, and expected output. 3. Run step by step, and adjust priorities when blockers, risks, or scope changes appear. ## Workflow Steps - `accessibility-testing.md` - `ai-assisted-testing.md` - `api-testing.md` - `automation-testing.md` - `bug-reporting.md` - `functional-testing.md` - `manual-testing.md` - `requirements-analysis.md` - `test-case-writing.md` - `test-reporting.md` - `test-strategy.md` ## Reference Files - `prompts/`: prompt files used by this skill. - `reference.md`: step-to-prompt mapping and workflow routing. - `references/`: supporting notes loaded only when needed. - `scripts/`: helper scripts or converters for this skill. ## Common Pitfalls - Do not jump into execution before confirming the current step. - Do not try to run the whole workflow with one giant prompt. - Do not ignore blockers and reprioritization. ## Best Practices - Start from the prompt file, then add only the context that matters. - Keep the output risk-driven and executable. - If the request is incomplete, return a usable first version and mark gaps.