placeholder-probe
SolidRender-time placeholder precondition probe for issue
Install
Quality Score: 87/100
Skill Content
Details
- Author
- The01Geek
- Repository
- The01Geek/prflow
- Created
- 3 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
probe
How to run the test-plugin probe and read its report — which field verifies which part of the docs/262 plugin usage contract.
ce-probe-sec
Security-probe a running target — web/API apps or CLI binaries — passive recon by default; smell-test and active-exploit tiers behind explicit opt-in. Twice-attested consent; refuses production; sandboxes binaries; findings, not verdicts. Triggers: security-test/sec-scan/probe a running app for vulnerabilities. Never production. For performance use /core-engineering:ce-probe-perf.
point-the-cheap-probes-at-young-code
Use when you need to FIND work in an unfamiliar repo rather than pick it off a tracker — a new house, or one whose issue backlog is claimed faster than you can read it. Four probes cost minutes each and need no domain knowledge: does any test fail when run alone, does the suite survive a shuffled order, does the race detector fire, does a fuzz target crash. Each one asserts on the SELECTOR'S YIELD, never on the exit code, because every runner treats "matched nothing" as success. And the yield of these probes is a function of the codebase's age and hardening, not of your effort: four probes over a thirteen-year-old repo with OSS-Fuzz integration found nothing in an hour, and the same shuffle probe found a real defect on a three-year-old fork in one run. Trigger terms: new repo, where do I start, find a bug, no good first issues, backlog is claimed, flaky, test isolation, order dependent, -shuffle, -race, go test, cargo test, runtest.