Generate a manual testing guide from a PR/MR diff.
npx skills add https://github.com/Dawn-Technology/aicelerate --skill test-pr-guide
Please help me install this Agent Skill. Skill: test-pr-guide Source: https://github.com/Dawn-Technology/aicelerate/tree/main/plugins/aimate/skills/test-pr-guide Command: npx skills add https://github.com/Dawn-Technology/aicelerate --skill test-pr-guide
It helps you confidently verify that a pull request actually works by converting the branch diff into a step-by-step manual testing guide that a human can follow.
Ask the agent: "Create a manual testing guide for this PR, using the branch diff, with setup steps and expected outcomes for QA to verify the fix."
High-intent search queries and answers about installing and using this skill.
Manual test scenario generation from a pull request diff involves parsing the changed code to map affected behaviors to concrete, repeatable test steps. The guide includes prerequisites, happy paths, edge cases, regression checks, expected results, and cleanup procedures.
Yes, you can create a QA checklist for a GitLab merge request automatically. By supplying the MR URL, the tool uses GitLab MCP to parse the diff and generates a structured QA checklist covering feature validation, bug-fix verification, and regression testing.
Regression testing for non-user-visible code changes validates internal refactors like logging or metrics updates through their observable effects. The testing guide maps these indirect changes to specific verification steps to ensure system stability.
You do not need a local git repository to generate test plans if you provide a GitLab MR URL. The tool fetches the diff via GitLab MCP. If no URL is provided, it falls back to parsing the diff via local git commands.
Diff analysis determines manual testing setup steps by scanning your project infrastructure files like docs, Makefile, package manifests, and environment examples. It extracts exact prerequisite commands and configurations required to validate the changed behaviors.
The best way to verify bug fixes in a pull request is using a diff-driven manual testing guide. It converts branch changes into step-by-step validation scenarios, covering happy paths and edge cases, to confirm the fix works without introducing regressions.
Dawn-TechnologyCreate a feature branch, commit changes, push, and open a GitLab Merge Request.
crsieblerControl a Chrome browser to validate frontend features via manual UI interactions.
robertolopezlopezFetch and normalize GitLab merge request metadata, comments, and discussions.
tuanemuyGenerate manual-test documentation from spec artifacts into spec/manual-tests.
