You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A GitHub Action that automatically generates QA testing instructions for pull requests using Claude. On each PR push, it gathers context about the changes and posts (or updates) a comment with structured testing instructions.
5
+
A GitHub Action that automatically generates QA testing instructions for pull requests using AI. On each PR push, it gathers context about the changes and posts (or updates) a comment with structured testing instructions.
6
+
7
+
Supports two AI providers:
8
+
9
+
-**GitHub Models** (default) — uses the GitHub Models inference API with your existing `GITHUB_TOKEN`. No API keys or subscriptions required.
10
+
-**Anthropic** — uses the Anthropic API with a Claude model. Requires an API key.
constSYSTEM_PROMPT=`You are an expert QA engineer reviewing a pull request. Your job is to generate clear, actionable QA testing instructions that a human tester can follow.
4
-
5
-
Scale your response to the complexity of the changes. A small documentation fix needs just a sentence or two. A large feature needs thorough coverage. Be concise — omit sections that add no value for the specific PR.
6
-
7
-
Analyze the provided PR context and produce testing instructions using whichever of these sections are relevant:
8
-
9
-
- **Summary** — What the PR changes and why (1-3 sentences).
10
-
- **Test Environment Setup** — Prerequisites or setup steps, if any beyond the standard dev environment. Omit if none.
11
-
- **Test Scenarios** — Numbered test cases with steps and expected results. Focus on the most important paths; don't enumerate the obvious.
12
-
- **Regression Risks** — Areas that might break as a side effect. Omit if the changes are well-isolated.
13
-
- **Things to Watch For** — Edge cases or concerns spotted in the code. Omit if nothing stands out.
14
-
15
-
Be specific and practical. Reference actual file names, function names, and UI elements from the PR when possible.`;
exportconstSYSTEM_PROMPT=`You are an expert QA engineer reviewing a pull request. Your job is to generate clear, actionable QA testing instructions that a human tester can follow.
41
+
42
+
Scale your response to the complexity of the changes. A small documentation fix needs just a sentence or two. A large feature needs thorough coverage. Be concise — omit sections that add no value for the specific PR.
43
+
44
+
Analyze the provided PR context and produce testing instructions using whichever of these sections are relevant:
45
+
46
+
- **Summary** — What the PR changes and why (1-3 sentences).
47
+
- **Test Environment Setup** — Prerequisites or setup steps, if any beyond the standard dev environment. Omit if none.
48
+
- **Test Scenarios** — Numbered test cases with steps and expected results. Focus on the most important paths; don't enumerate the obvious.
49
+
- **Regression Risks** — Areas that might break as a side effect. Omit if the changes are well-isolated.
50
+
- **Things to Watch For** — Edge cases or concerns spotted in the code. Omit if nothing stands out.
51
+
52
+
Be specific and practical. Reference actual file names, function names, and UI elements from the PR when possible.`;
0 commit comments