zero-script-qa
Skill66 starsChanged 7 months agoApache-2.0View on GitHub
Zero Script QA - Testing methodology without test scripts. Uses structured JSON logging and real-time Docker monitoring.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- popup-studio-ai/bkit-claude-codetheir own version, first seen Oct 8, 2026
- ww-w-ai/bkit-claude-codetheir own version, first seen Aug 14, 2026
- ww-w-ai/bkit-codextheir own version, first seen Feb 23, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- popup-studio-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-codex★ 69same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- auditSkill
- batchSkill
- bkend-authSkill
- bkend-cookbookSkill
- bkend-dataSkill
- bkend-guidesSkill
- bkend-mcpSkill
- bkend-quickstartSkill
- bkend-securitySkill
- bkend-storageSkill
- bkit-rulesSkill
- bkit-templatesSkill
- btwSkill
- code-reviewSkill
- controlSkill
- deploySkill
- desktop-appSkill
- development-pipelineSkill
- dynamicSkill
- enterpriseSkill
- gemini-cli-learningSkill
- loopSkill
- mobile-appSkill
- output-style-setupSkill
- pdcaSkill
- phase-1-schemaSkill
- phase-2-conventionSkill
- phase-3-mockupSkill
- phase-4-apiSkill
- phase-5-design-systemSkill
- phase-6-ui-integrationSkill
- phase-7-seo-securitySkill
- phase-8-reviewSkill
- phase-9-deploymentSkill
- plan-plusSkill
- pm-discoverySkill
- qa-phaseSkill
- rollbackSkill
- simplifySkill
- skill-createSkill
- skill-statusSkill
- starterSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
Instead of writing and maintaining test scripts, Zero Script QA uses:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Zero Script QA
Testing methodology using structured logging instead of test scripts
Philosophy
Instead of writing and maintaining test scripts, Zero Script QA uses:
- Structured JSON logging for all operations
- Real-time Docker log monitoring
- Pattern-based verification
Key Principles
1. Structured Logging
// Every operation logs structured JSON
logger.info({
event: 'user.login',
userId: user.id,
method: 'email',
success: true,
duration: 234
});2. Log Patterns
Define expected patterns for verification:
{
"feature": "user-login",
"patterns": [
{"event": "user.login", "success": true},
{"event": "session.created"},
{"event": "audit.login"}
]
}3. Real-time Monitoring
# Monitor Docker logs in real-time
docker logs -f app-container 2>&1 | grep -E '"event":'Usage
# Start QA monitoring
/zero-script-qa start
# Monitor specific feature
/zero-script-qa monitor user-login
# Generate QA report
/zero-script-qa reportBenefits
| Traditional Testing | Zero Script QA |
| Write test scripts | Define log patterns |
| Maintain test code | Logs are automatic |
| Flaky tests | Consistent logs |
| Separate test env | Same as production |
Log Categories
- Business Events: User actions, transactions
- System Events: Startup, shutdown, errors
- Performance Metrics: Response times, throughput
- Security Events: Auth, access control
Integration
Works with:
- Docker Compose
- Kubernetes
- Any JSON logging system
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

