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.
Smoke test gate — verifies the application launches and critical paths are accessible before deeper QA
Install Corgispec QA Smoke
$ npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-smoke -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-smoke --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-smoke .claude/skills/corgispec-qa-smoke && 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-smoke" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-smoke into .claude/skills/corgispec-qa-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-smoke", 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-smokeType 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-smoke -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-smoke --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-smoke .agents/skills/corgispec-qa-smoke && 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-smoke" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-smoke into .agents/skills/corgispec-qa-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-smoke", 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-smoke -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-smoke --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-smoke .cursor/skills/corgispec-qa-smoke && 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-smoke" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-smoke into .cursor/skills/corgispec-qa-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-smoke", 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-smoke--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-smoke -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ricoyudog/Coding_Corgi_flow corgispec-qa-smoke --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-smoke .gemini/skills/corgispec-qa-smoke && 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-smoke" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-smoke into .gemini/skills/corgispec-qa-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-smoke", 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-smokeInstalls 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-smoke -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-smoke .github/skills/corgispec-qa-smoke && 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-smoke" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-smoke into .github/skills/corgispec-qa-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-smoke", 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-smoke -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-smoke --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-smoke .opencode/skills/corgispec-qa-smoke && 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-smoke" agent skill from https://github.com/ricoyudog/Coding_Corgi_flow/tree/master/.claude/skills/atoms/corgispec-qa-smoke into .opencode/skills/corgispec-qa-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corgispec-qa-smoke", 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-smoke- GitHub stars
- 104
- Token cost
- ~1k tokens
- SKILL.md length
- 476 words
- Files
- 2
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Smoke test gate — verifies the application launches and critical paths are accessible before deeper QA
- Works in 6 steps: Launch or confirm application is running → Verify build version → Check for runtime errors → …
- Tasks that involve QA and bug reports
- SKILL.md covers Overview, When to Use, Preconditions and Steps, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Corgispec QA Smoke is an agent skill from ricoyudog/Coding_Corgi_flow. Smoke test gate — verifies the application launches and critical paths are accessible before deeper QA
Its SKILL.md is about 1k 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: Requires a running or launchable application. Called before any deeper QA testing begins.
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-smoke”
Requirements
- Compatibility (from SKILL.md): Requires a running or launchable application. Called before any deeper QA testing begins.
Workflow steps
6 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
Requires a running or launchable application. Called before any deeper QA testing begins.
From compatibility in the SKILL.md frontmatter.
Context cost
Corgispec QA Smoke loads about 1k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 476 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). 476 words, ~1,021 tokens.
Download SKILL.mdSave it as
.claude/skills/corgispec-qa-smoke/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- corgispec-qa-smoke
- description
- Smoke test gate — verifies the application launches and critical paths are accessible before deeper QA
- compatibility
- Requires a running or launchable application. Called before any deeper QA testing begins.
- license
- MIT
- metadata.author
- corgispec
- metadata.version
- 1.0.0
- metadata.generatedBy
- 1.0.0
Smoke Test Gate
"Does it even launch?" — The first gate in any QA cycle.
Overview
This skill executes a minimal smoke test to confirm the application is functional at the most basic level before investing time in deeper QA. If smoke fails, all further testing is aborted — there is no point testing features on a broken build.
A smoke pass means:
- The application starts without crashing
- No HTTP 500 errors on critical endpoints
- No unhandled runtime exceptions in logs
- Critical navigation paths are reachable
- Build version matches the expected release
When to Use
- As the first step after deploying or launching a build for QA
- Before executing any test cases from
qa-testcases.md - After a hotfix deployment to confirm basic stability
- When a QA session begins and you need a go/no-go decision
Do NOT use this skill for deep functional testing, regression, or performance validation.
Preconditions
- Application is deployed or can be launched locally
- Expected build version is known (from tasks.md, release tag, or deploy log)
- Critical paths are identified (login page, main dashboard, primary API health endpoint)
Steps
1. Launch or confirm application is running
Start the application (or confirm the deployed instance is reachable):
- Web app: verify the root URL returns HTTP 200
- API service: verify the health/status endpoint responds
- CLI tool: verify
--versionor--helpexecutes without error
If the app fails to start or the URL is unreachable, FAIL immediately.
2. Verify build version
Confirm the running instance matches the expected version:
- Check version endpoint, page footer, response headers, or CLI output
- Compare against the expected version from the change artifacts
If version does not match, FAIL — wrong build is deployed.
Show full SKILL.md (202 more words)Show less
3. Check for runtime errors
Inspect available logs (console, server logs, browser devtools) for:
- Unhandled exceptions or stack traces
- Fatal errors during startup
- Critical dependency failures (DB connection, auth service)
If critical errors are present, FAIL.
4. Verify critical paths are accessible
Navigate or request each critical path:
- Authentication page loads (if applicable)
- Main dashboard/home page renders
- Primary API endpoints return expected status codes (200/201, not 500/503)
- No blank pages or broken layouts on key screens
If any critical path returns 500 or fails to render, FAIL.
5. Read assigned test cases
If qa-testcases.md exists in the change directory:
- Read the file and identify cases assigned to the current smoke scope
- Execute only cases tagged
[smoke]or explicitly listed for this gate - Record pass/fail for each
6. Report result
Produce a smoke report in this format:
## Smoke Test Report
- **Build Version:** <actual> (expected: <expected>)
- **Timestamp:** <ISO 8601>
- **Result:** PASS | FAIL
### Checks
| Check | Status | Notes |
|-------|--------|-------|
| App launches | PASS/FAIL | <detail> |
| Version match | PASS/FAIL | <detail> |
| No runtime errors | PASS/FAIL | <detail> |
| Critical path: <name> | PASS/FAIL | <detail> |
| ... | ... | ... |
### Decision
- **PASS** → Proceed to full QA test cases
- **FAIL** → Abort QA. Reason: <summary>Common Mistakes
- Testing too deeply — Smoke is not regression. Only check "does it launch and respond." Move on quickly.
- Ignoring version mismatch — Testing the wrong build wastes everyone's time. Always verify version first.
- Skipping log inspection — An app can return 200 while throwing errors internally. Check logs.
- Continuing after failure — If smoke fails, STOP. Do not proceed to deeper QA. Report and block.
© 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-smoke of ricoyudog/Coding_Corgi_flow.
- SKILL.md
- skill.meta.json
Open the folder on GitHubat commit 461555c
Compare with similar skills
Corgispec QA Smoke 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 Smoke this skillricoyudog/Coding_Corgi_flow | 104 | — | ~1k | 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 | 449 | — | ~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 Smoke
What does Corgispec QA Smoke do?
Smoke test gate — verifies the application launches and critical paths are accessible before deeper QA. Corgispec QA Smoke is an agent skill from ricoyudog/Coding_Corgi_flow.
When should I use Corgispec QA Smoke?
Corgispec QA Smoke fits situations like: tasks that involve QA and bug reports.
How do I install Corgispec QA Smoke in Claude Code?
Run `npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-smoke -a claude-code`. Or copy the skill folder (.claude/skills/atoms/corgispec-qa-smoke in ricoyudog/Coding_Corgi_flow) into .claude/skills/corgispec-qa-smoke in your project. Claude Code loads it when a task matches its description.
How do I install Corgispec QA Smoke in Codex?
Run `npx skills add ricoyudog/Coding_Corgi_flow --skill corgispec-qa-smoke -a codex`. Or copy the skill folder (.claude/skills/atoms/corgispec-qa-smoke in ricoyudog/Coding_Corgi_flow) into .agents/skills/corgispec-qa-smoke in your project. Codex loads it when a task matches its description.
Can I use Corgispec QA Smoke 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-smoke -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-smoke, .gemini/skills/corgispec-qa-smoke, .github/skills/corgispec-qa-smoke and .opencode/skills/corgispec-qa-smoke in your project.
What does Corgispec QA Smoke need to run?
SKILL.md names no scripts, command-line tools or credentials: Corgispec QA Smoke is instructions for the agent only. Compatibility (from SKILL.md): Requires a running or launchable application. Called before any deeper QA testing begins..
Does Corgispec QA Smoke 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 Smoke 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 Smoke use?
Corgispec QA Smoke 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 Smoke use?
About 1k tokens (SKILL.md is roughly 4.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 Smoke?
Skills that share tags, products or a category with Corgispec QA Smoke: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Moav E2E (MotherofallVPNs/MoaV, 449 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 Smoke?
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.