qa-analyst
Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect. Also use for post-merge PR review analysis: auditing recent closed PRs for Devin/GitHub/security bot comments, verifying whether requested corrections were applied, and turning pending fixes into S
as observed 2026-10-03T08:46:10.142Z- Identifier
qa-analyst- Source
- ClawHub
- Version observed
- 1.0.9
- Source repository
- not published
- Repository observation
- No source repository listed
- First observed here
- 2026-09-10T12:18:05.764Z
- Observations recorded
- 6
- Installs (reported upstream)
- 0
- Weekly downloads (upstream)
- 212
- Declared license
- MIT-0
Observation history
2026-10-03T08:46:10.142Z
Fields that differed: changelog latestVersion summary
| Field | Before | After |
|---|---|---|
changelog |
"- Updated skill documentation with expanded QA process details, new best practices, and clarified untrusted input handling.\n- Defined the QA cycle phases (requirements analysis, | "Version 1.0.9 Changelog:\n\n- Added comprehensive SKILL.md documentation outlining use cases, QA cycle, and core responsibilities for the qa-analyst skill.\n- Clarified when to us |
latestVersion |
"1.0.8" | "1.0.9" |
summary |
"Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect." | "Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect. Also use for post-merge PR review analysis: auditing recent closed PRs for D |
2026-09-17T19:21:47.048Z
Fields that differed: license description
| Field | Before | After |
|---|---|---|
license |
null | "MIT-0" |
description |
"Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect." | null |
2026-09-15T17:18:40.381Z
Fields that differed: changelog latestVersion
| Field | Before | After |
|---|---|---|
changelog |
"- Updated metadata version to 1.1.1 and made skill publicly visible.\n- Enhanced documentation to clarify QA cycle phases, including requirements analysis, test planning, test cas | "- Updated skill documentation with expanded QA process details, new best practices, and clarified untrusted input handling.\n- Defined the QA cycle phases (requirements analysis, |
latestVersion |
"1.0.7" | "1.0.8" |
2026-09-13T15:17:50.529Z
Fields that differed: changelog latestVersion
| Field | Before | After |
|---|---|---|
changelog |
"- Updated skill documentation with detailed QA cycle, test planning strategies, and bug reporting workflows.\n- Clarified the skill's use of Portuguese for user interactions and E | "- Updated metadata version to 1.1.1 and made skill publicly visible.\n- Enhanced documentation to clarify QA cycle phases, including requirements analysis, test planning, test cas |
latestVersion |
"1.0.5" | "1.0.7" |
2026-09-12T14:17:54.398Z
Fields that differed: changelog description latestVersion summary
| Field | Before | After |
|---|---|---|
changelog |
"- Added comprehensive usage instructions clarifying the QA analysis workflow, including requirement review, test planning, case creation, execution, bug reporting, and process imp | "- Updated skill documentation with detailed QA cycle, test planning strategies, and bug reporting workflows.\n- Clarified the skill's use of Portuguese for user interactions and E |
description |
"Use when the user asks for QA analysis, requirement review, test planning, test cases, bug reports, root-cause analysis of defects, or mentions QA, quality assurance, testar essa | "Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect." |
latestVersion |
"1.0.1" | "1.0.5" |
summary |
"Use when the user asks for QA analysis, requirement review, test planning, test cases, bug reports, root-cause analysis of defects, or mentions QA, quality assurance, testar essa | "Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect." |
Correction
If you maintain this extension and believe anything above is inaccurate, request a correction. Corrections are published, and disputed entries are marked as disputed while under review.