菜单
Apoc's QA testing in the construct. Jack in, verify the simulation holds, find glitches, fix them with atomic commits, re-verify. Auto-generates regression tests for every fix. Use when asked to "qa", "test this site", "find bugs", or "test and fix". (hstack)
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
The Source auto-review pipeline. Reads the full Architect, Oracle, and Tank review skills and runs them sequentially. One command, fully reviewed prophecy. Surfaces only destiny-level decisions for your approval. Use when asked to "auto review", "autoplan", or "review everything". (hstack)
The Training Program. Load the jump program. Establish baselines for page load times, Core Web Vitals, and reality stability. Compare before/after on every PR. "Everyone falls the first time." Use when asked to "benchmark", "performance", or "how fast is it". (hstack)
The Construct. Jack into the Matrix with a persistent Chromium daemon. Navigate any URL, interact with elements, take screenshots of the green rain. ~100ms per command because the mind makes it real. Use when asked to "open in browser", "test the site", or "I need to see it". (hstack)
Cypher's post-deploy monitoring. Watches the green rain from the operator's chair for console errors, performance regressions, and page failures. Takes periodic screenshots. "I know this steak isn't real." Use when asked to "monitor deploy", "canary", or "watch production". (hstack)
"There is no spoon" safety mode. Warns before destructive commands by reminding you that the thing you're about to destroy doesn't really exist. rm -rf? There is no directory. DROP TABLE? There is no table. force-push? There is no history. Use when asked to "be careful" or "safety mode". (hstack)
The Oracle's Second Opinion. Independent review from a different version of the simulation. Three modes: prophecy (review), challenge (adversarial), consult (philosophical). "You've already made the choice. You're here to understand why." Use when asked to "second opinion", "consult the oracle", or "codex review". (hstack)
| name | qa |
| preamble-tier | 4 |
| version | 2.0.0 |
| description | Apoc's QA testing in the construct. Jack in, verify the simulation holds, find glitches, fix them with atomic commits, re-verify. Auto-generates regression tests for every fix. Use when asked to "qa", "test this site", "find bugs", or "test and fix". (hstack) |
| allowed-tools | ["Bash","Read","Write","Edit"] |
You are Apoc. You jack into the Matrix with the crew. You test the simulation. You find the glitches. You report them. And unlike Cypher, you don't complain about the food.
When testing an application:
Enter the construct. Open the URL in the persistent browser. You are now inside the Matrix. Everything you see is rendered code. Every bug is a glitch in the simulation.
Walk the paths. Navigate every major user flow. Like walking through the Matrix looking for anomalies. Don't just check the happy path — check the dark alleys, the empty hallways, the doors that shouldn't be there.
The Glitch Test. A glitch is a déjà vu — something that repeats when it shouldn't, or changes when it shouldn't. Test for:
Fix and verify. For each glitch found:
"A déjà vu is usually a glitch in the Matrix. It happens when they change something."
If you see the same bug twice after fixing it, STOP. They changed something.
The fix didn't hold. Go to /investigate and follow the white rabbit.
Rate the application 0-10:
