Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
SBTM-style exploratory testing session — charter-driven, tour-guided, time-boxed human investigation
Install Corgispec QA Exploratory
$ npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-exploratory -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-exploratory --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ricoyudog/Coding_Corgi_flow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/atoms/corgispec-qa-exploratory .claude/skills/corgispec-qa-exploratory && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "corgispec-qa-exploratory" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-exploratory into .claude/skills/corgispec-qa-exploratory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-exploratory", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-exploratoryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-exploratory -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-exploratory --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ricoyudog/Coding_Corgi_flow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/atoms/corgispec-qa-exploratory .agents/skills/corgispec-qa-exploratory && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "corgispec-qa-exploratory" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-exploratory into .agents/skills/corgispec-qa-exploratory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-exploratory", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-exploratory -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-exploratory --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ricoyudog/Coding_Corgi_flow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/atoms/corgispec-qa-exploratory .cursor/skills/corgispec-qa-exploratory && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "corgispec-qa-exploratory" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-exploratory into .cursor/skills/corgispec-qa-exploratory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-exploratory", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ricoyudog/Coding_Corgi_flow.git --path .claude/skills/atoms/corgispec-qa-exploratory--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-exploratory -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-exploratory --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ricoyudog/Coding_Corgi_flow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/atoms/corgispec-qa-exploratory .gemini/skills/corgispec-qa-exploratory && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "corgispec-qa-exploratory" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-exploratory into .gemini/skills/corgispec-qa-exploratory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-exploratory", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-exploratoryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-exploratory -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ricoyudog/Coding_Corgi_flow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/atoms/corgispec-qa-exploratory .github/skills/corgispec-qa-exploratory && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "corgispec-qa-exploratory" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-exploratory into .github/skills/corgispec-qa-exploratory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-exploratory", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-exploratory -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-exploratory --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ricoyudog/Coding_Corgi_flow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/atoms/corgispec-qa-exploratory .opencode/skills/corgispec-qa-exploratory && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "corgispec-qa-exploratory" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-exploratory into .opencode/skills/corgispec-qa-exploratory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-exploratory", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
corgispec-qa-exploratory- GitHub stars
- 104
- Token cost
- ~1.5k tokens
- SKILL.md length
- 606 words
- Files
- 2
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
SBTM-style exploratory testing session — charter-driven, tour-guided, time-boxed human investigation
- Works in 5 steps: Read the Charter → Select Tours (2–4) → Explore Systematically → …
- Tasks that involve QA and bug reports
- SKILL.md covers Overview, Session Structure (45–75…, The 12 Test Tours and Steps, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Corgispec QA Exploratory is an agent skill from ricoyudog/Coding_Corgi_flow. SBTM-style exploratory testing session — charter-driven, tour-guided, time-boxed human investigation
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`). Compatibility notes: Universal. Works with any codebase or platform.
It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: OpenSpec GitFlow — structured AI engineering workflows with issue tracking. The licence is MIT.
When your agent uses it
- Tasks that involve QA and bug reports
Example prompts
- “/corgispec-qa-exploratory”
Requirements
- Compatibility (from SKILL.md): Universal. Works with any codebase or platform.
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 461555c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Universal. Works with any codebase or platform.
From compatibility in the SKILL.md frontmatter.
Context cost
Corgispec QA Exploratory loads about 1.5k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 606 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ricoyudog/Coding_Corgi_flow at commit 461555c, republished under its MIT licence (© ricoyudog). 606 words, ~1,523 tokens.
Download SKILL.mdSave it as
.claude/skills/corgispec-qa-exploratory/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- corgispec-qa-exploratory
- description
- SBTM-style exploratory testing session — charter-driven, tour-guided, time-boxed human investigation
- compatibility
- Universal. Works with any codebase or platform.
- license
- MIT
- metadata.author
- corgispec
- metadata.version
- 1.0.0
- metadata.generatedBy
- 1.0.0
Exploratory Testing — SBTM Session
Overview
Session-Based Test Management (SBTM), developed by James Bach and Michael Bolton, structures exploratory testing into accountable, time-boxed sessions. Each session has a charter (mission), uses one or more Test Tours to guide exploration, and produces a debrief report with findings and coverage notes.
Exploratory testing is simultaneous learning, test design, and test execution. It is not ad-hoc — it is disciplined investigation guided by heuristics and documented in real time.
Session Structure (45–75 minutes)
| Phase | Duration | Activity |
|---|---|---|
| Charter | 5 min | Define mission, scope, and success criteria |
| Explore | 30–55 min | Systematic investigation using selected tours |
| Note | Continuous | Record observations, findings, questions as they occur |
| Debrief | 10–15 min | Summarize coverage, findings, and next steps |
The 12 Test Tours
Select 2–4 tours per session based on the change context.
| # | Tour | Description | When to Recommend |
|---|---|---|---|
| 1 | Business District | Exercise key business flows end-to-end | All changes — validates core value paths |
| 2 | Money | Probe revenue-related features (payments, subscriptions, pricing) | Payment/billing changes |
| 3 | Bad Neighborhood | Focus on historically buggy areas | Historically buggy modules |
| 4 | Historical | Revisit past bug clusters and regressions | Legacy code changes |
| 5 | FedEx | Track data as it flows through the entire system | Full-stack or integration changes |
| 6 | Rained-Out | Explore failure modes, error handling, edge cases | All changes — validates resilience |
| 7 | Obsessive-Compulsive | Repeat operations rapidly, vary sequences | Loops, batch processing, concurrency |
| 8 | Garbage Collector | Test cleanup, boundaries, limits, resource exhaustion | CRUD operations, resource management |
| 9 | Intellectual | Challenge complex logic with tricky inputs and edge cases | Algorithms, business rules, calculations |
| 10 | Couch Potato | Take the minimal effort path, use defaults only | UX flows, onboarding, happy paths |
| 11 | Landmark | Navigate via key features and integration points | New features, UI navigation |
| 12 | Museum | Examine help docs, examples, error messages, tooltips | SDK, library, or API documentation |
Steps
1. Read the Charter
If called from a molecule (e.g., corgispec-qa-session), read the charter provided. Otherwise, define your own charter:
- Mission: What are you investigating?
- Scope: Which areas/features are in-bounds?
- Out of scope: What to explicitly avoid this session?
Show full SKILL.md (275 more words)Show less
2. Select Tours (2–4)
Choose 2 to 4 tours from the table above based on the change context. Different scenarios call for different Tour strategies:
- Bug fix → apply Bad Neighborhood Tour + Historical Tour + Rained-Out Tour
- New feature → apply Landmark Tour + Business District Tour + Couch Potato Tour
- Refactor → apply FedEx Tour + Obsessive-Compulsive Tour + Intellectual Tour
- Payment change → apply Money Tour + Rained-Out Tour + Business District Tour
- Full-stack change → apply FedEx Tour + Business District Tour + Rained-Out Tour
- CRUD/management → apply Garbage Collector Tour + Obsessive-Compulsive Tour + Museum Tour
3. Explore Systematically
For each selected tour:
- State which tour you are executing
- Identify specific test ideas within that tour's lens
- Execute tests, varying inputs and sequences
- Note observations immediately — do not defer
4. Record Findings with Severity
Classify each finding:
| Severity | Definition |
|---|---|
| Blocker | Prevents core functionality, no workaround |
| Critical | Major feature broken, workaround exists but unacceptable |
| Major | Significant issue affecting user experience |
| Minor | Small defect, cosmetic, or low-impact behavioral issue |
| Trivial | Nitpick, suggestion, or style concern |
5. Assemble Debrief
Compile the session report (see Reporting format below).
Reading qa-testcases.md
If the change directory contains qa-testcases.md, read it before starting exploration. Use the documented test cases as a baseline — your exploratory session extends beyond them, finding what structured cases miss.
Reporting Format
## Exploratory Test Session Report
- **Session ID**: ET-{YYYY-MM-DD}-{NNN}
- **Charter**: {mission statement}
- **Duration**: {actual minutes} / {planned minutes}
- **Tours Used**: {list of tours selected}
### Coverage
{Areas explored, features touched, paths taken}
### Findings
| # | Severity | Tour | Finding | Evidence |
|---|----------|------|---------|----------|
| 1 | major | FedEx | Data lost between step X and Y | screenshot/log ref |
### Oddities
{Things that aren't bugs but seem wrong, surprising, or worth investigating later}
### Debrief
- **Coverage confidence**: {low/medium/high} — {why}
- **Areas not reached**: {what was skipped and why}
- **Recommendations**: {follow-up sessions, automated tests to add, areas needing deeper review}
### Evidence
{Links to screenshots, logs, recordings, or reproduction steps}When to Use
- After code changes are applied and you need human-style investigation
- When automated tests pass but confidence in quality is low
- For areas with no existing test coverage
- When a molecule skill requests exploratory QA
When NOT to Use
- For writing automated test scripts (use TDD skill instead)
- For test planning without execution (use qa-plan skill instead)
- As a replacement for structured regression testing
© ricoyudog, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .claude/skills/atoms/corgispec-qa-exploratory of ricoyudog/Coding_Corgi_flow.
- SKILL.md
- skill.meta.json
Open the folder on GitHubat commit 461555c
Compare with similar skills
Corgispec QA Exploratory next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Corgispec QA Exploratory this skillricoyudog/Coding_Corgi_flow | 104 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Moav E2EMotherofallVPNs/MoaV | 448 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Creating A Coral TaskHuman-Agent-Society/CORAL | 1.1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Launch Rlmarin-community/marin | 3.9k | — | ~894 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
Creating A Coral Task
Human-Agent-Society/CORAL
Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…
Launch Rl
marin-community/marin
Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.
Actionbook Web Test
actionbook/actionbook
Run browser-based web tests against websites using Actionbook CLI.
More from ricoyudog/Coding_Corgi_flow
All 18 skills in this repoCorgispec Propose
ricoyudog/Coding_Corgi_flow
Create or complete one RFC-first CorgiSpec planning package from an accepted unbound RFC Slice or a closed maintenance exemption.
Corgispec Update
ricoyudog/Coding_Corgi_flow
Reconcile an existing CorgiSpec planning package after intent, requirements, scenarios, design, or task sequencing changes.
Corgispec Ask
ricoyudog/Coding_Corgi_flow
Answer pending Obsidian questions from CorgiSpec Memory/Wiki with early-stop retrieval, source citations, and a strict file budget.
Corgispec Install
ricoyudog/Coding_Corgi_flow
A skill your agent uses when installing, updating, or verifying this repo's project-local Corgi GitFlow assets in a target project.
Corgispec Lint
ricoyudog/Coding_Corgi_flow
Validate CorgiSpec v4 Memory/Wiki structure, freshness, source integrity, delivery extraction, bridge drift, and legacy preservation.
Corgispec Rfc
ricoyudog/Coding_Corgi_flow
Guide a human-authored CorgiSpec RFC through isolated draft creation, validation, explicit interactive approval, merge effectiveness, collision renumbering, and amendments.
Related
Categories
Questions about Corgispec QA Exploratory
What does Corgispec QA Exploratory do?
SBTM-style exploratory testing session — charter-driven, tour-guided, time-boxed human investigation. Corgispec QA Exploratory is an agent skill from ricoyudog/Coding_Corgi_flow.
When should I use Corgispec QA Exploratory?
Corgispec QA Exploratory fits situations like: tasks that involve QA and bug reports.
How do I install Corgispec QA Exploratory in Claude Code?
Run `npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-exploratory -a claude-code`. Or copy the skill folder (.claude/skills/atoms/corgispec-qa-exploratory in ricoyudog/Coding_Corgi_flow) into .claude/skills/corgispec-qa-exploratory in your project. Claude Code loads it when a task matches its description.
How do I install Corgispec QA Exploratory in Codex?
Run `npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-exploratory -a codex`. Or copy the skill folder (.claude/skills/atoms/corgispec-qa-exploratory in ricoyudog/Coding_Corgi_flow) into .agents/skills/corgispec-qa-exploratory in your project. Codex loads it when a task matches its description.
Can I use Corgispec QA Exploratory in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-exploratory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/corgispec-qa-exploratory, .gemini/skills/corgispec-qa-exploratory, .github/skills/corgispec-qa-exploratory and .opencode/skills/corgispec-qa-exploratory in your project.
What does Corgispec QA Exploratory need to run?
SKILL.md names no scripts, command-line tools or credentials: Corgispec QA Exploratory is instructions for the agent only. Compatibility (from SKILL.md): Universal. Works with any codebase or platform..
Does Corgispec QA Exploratory access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Corgispec QA Exploratory safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Corgispec QA Exploratory use?
Corgispec QA Exploratory is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Corgispec QA Exploratory use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Corgispec QA Exploratory?
Skills that share tags, products or a category with Corgispec QA Exploratory: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Moav E2E (MotherofallVPNs/MoaV, 448 stars) and Creating A Coral Task (Human-Agent-Society/CORAL, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Corgispec QA Exploratory?
ricoyudog (a GitHub user) maintains it in ricoyudog/Coding_Corgi_flow, which has 104 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on August 19, 2026.
Source: ricoyudog/Coding_Corgi_flow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.