Coding & Debugging
PromptBeginner5 minmarkdown
- **Analyze coverage gaps** by identifying untested code paths
missing edge case tests
0
Explore
Find agent skills by outcome
11,431 skills indexed with the new KISS metadata standard.
Showing 24 of 11,431Categories: Openclaw, Communication, Coding & Debugging, Creative
Coding & Debugging
PromptBeginner5 minmarkdown
**RULE:** When using this prompt
you must create a file named `TODO_quality-engineering.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,...
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Treat test infrastructure as a first-class engineering concern with versioning
review
0
Coding & Debugging
PromptBeginner5 minmarkdown
- [ ] Coverage references cite relevant code areas
services
0
Coding & Debugging
PromptBeginner5 minmarkdown
In `TODO_quality-engineering.md`
include:
0
Creative
PromptBeginner5 minmarkdown
- Store test artifacts (reports
screenshots
0
Creative
PromptBeginner5 minmarkdown
- Simulate partial and cascading failures
not just complete outages
0
Communication
PromptBeginner5 minmarkdown
- Ensure contract tests cover all inter-service communication
not just happy paths
0
Creative
PromptBeginner5 minmarkdown
- [ ] CI/CD pipeline design includes parallelization
time budgets
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Design chaos engineering experiments: fault injection
failure scenarios
0
Creative
PromptBeginner5 minmarkdown
- Design CI pipeline with test stages
execution order
0
Creative
PromptBeginner5 minmarkdown
- Design observability dashboards for test results
trends
0
Creative
PromptBeginner5 minmarkdown
- Design the test pyramid with coverage targets per layer (unit
integration
0
Coding & Debugging
PromptBeginner5 minmarkdown
Quality Engineering Agent Role
# Quality Engineering Request
0
Coding & Debugging
PromptBeginner5 minmarkdown
You are a senior quality engineering expert and specialist in risk-based test strategy
test automation architecture
0
Coding & Debugging
PromptBeginner5 minmarkdown
**RULE:** When using this prompt
you must create a file named `TODO_api-tester.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaandemi...
0
Coding & Debugging
PromptBeginner5 minmarkdown
Use checkboxes and stable IDs (e.g.
`APIT-ITEM-1.1`):
0
Coding & Debugging
PromptBeginner5 minmarkdown
Use checkboxes and stable IDs (e.g.
`APIT-PLAN-1.1`):
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Summary of API endpoints
architecture
0
Coding & Debugging
PromptBeginner5 minmarkdown
Write all proposed test plans and any code snippets to `TODO_api-tester.md` only. Do not create any other files. If specific files should be created or edited
include patch-style diffs or clearly labeled file blocks inside the TODO.
0
Coding & Debugging
PromptBeginner5 minmarkdown
In `TODO_api-tester.md`
include:
0
Creative
PromptBeginner5 minmarkdown
- Include visual trend charts showing latency
throughput
0
Coding & Debugging
PromptBeginner5 minmarkdown
After completing API testing
verify:
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Throughput**: Read-heavy APIs >1000 RPS per instance
write-heavy APIs >100 RPS per instance
0