agentleFS
ww-w-aiww-w-ai/bkit-gemini/skills/zero-script-qa/SKILL.md

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

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
  1. Distinctive:

    Instead of writing and maintaining test scripts, Zero Script QA uses:

    line 48

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Zero Script QA

Testing methodology using structured logging instead of test scripts

Philosophy

Instead of writing and maintaining test scripts, Zero Script QA uses:

  1. Structured JSON logging for all operations
  2. Real-time Docker log monitoring
  3. 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 report

Benefits

Traditional TestingZero Script QA
Write test scriptsDefine log patterns
Maintain test codeLogs are automatic
Flaky testsConsistent logs
Separate test envSame as production

Log Categories

  1. Business Events: User actions, transactions
  2. System Events: Startup, shutdown, errors
  3. Performance Metrics: Response times, throughput
  4. Security Events: Auth, access control

Integration

Works with:

  • Docker Compose
  • Kubernetes
  • Any JSON logging system

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.