Skip to content

heliohq/ship / skills/qa

Runtime QA of a change: start the app, test acceptance criteria and edge cases, and report evidence. Use for "test this", "QA", "does it work", exploratory checks, or post-review runtime verification. Not static code review.

FileKindSize
SKILL.mdskill md8.0 KB
references/api.mdmarkdown4.5 KB
references/browser.mdmarkdown9.5 KB
references/cli.mdmarkdown5.4 KB
references/electron.mdmarkdown3.7 KB
references/report.mdmarkdown2.5 KB

references/report.md

View on GitHub
# Report Template

Shared report structure for all testing references (browser, API, CLI).
Each reference writes its report to `<qa_dir>/` using this template
with type-specific metadata fields.

## Issue severity (shared definitions)

| Severity | Definition |
|----------|------------|
| **critical** | Blocks a core workflow, causes data loss, or crashes the app |
| **high** | Major feature broken or unusable, no workaround |
| **medium** | Feature works but with noticeable problems, workaround exists |
| **low** | Minor cosmetic or polish issue |

## Report structure

```markdown
# {Type} Exploratory Report

| Field | Value |
|-------|-------|
| **Date** | {YYYY-MM-DD HH:MM UTC} |
{type-specific metadata fields — see below}

## Summary

| Severity | Count |
|----------|-------|
| Critical | 0 |
| High | 0 |
| Medium | 0 |
| Low | 0 |
| **Total** | **0** |

## Issues

### ISSUE-001: {Short title}

| Field | Value |
|-------|-------|
| **Severity** | critical / high / medium / low |
| **Category** | {from the reference's category list} |
{type-specific issue fields — see below}

**Expected**

{What should happen}

**Observed**

{What actually happened}

**Evidence**

{Screenshots, videos, curl output, command output — linked by relative path}

---
```

## Type-specific fields

### Browser (`browser-report.md`)

Metadata:
- **App URL** | {URL}
- **Session** | {SESSION_NAME}
- **Scope** | {what was explored}

Issue fields:
- **URL** | {page URL where issue was found}
- **Repro Video** | {path to video, or N/A for static issues}

Evidence format: numbered repro steps with screenshot at each step,
repro video for interactive issues.

### API (`api-report.md`)

Metadata:
- **Base URL** | http://localhost:{PORT}
- **Scope** | {endpoints tested}

Issue fields:
- **Endpoint** | {METHOD /path}
- **Evidence** | [api-{test-name}.txt](api-{test-name}.txt)

Evidence format: full curl request/response captured with `curl -sv`.

### CLI (`cli-report.md`)

Metadata:
- **CLI** | {command name and version}
- **Scope** | {commands/subcommands tested}

Issue fields:
- **Command** | {full command that triggers the issue}
- **Evidence** | [cli-{test-name}.txt](cli-{test-name}.txt)
- **Exit code** | {actual} (expected: {expected})

Evidence format: stdout + stderr + exit code captured to file.

## Rules

- Increment issue counter: ISSUE-001, ISSUE-002, ...
- Append each issue immediately as found — do not batch
- Update summary severity counts after all issues are documented
- Every `### ISSUE-` block must be reflected in the summary totals
- Link evidence files by relative path
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall