placeholder-probe

Solid

Render-time placeholder precondition probe for issue

Code & Development 115 stars 41 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
69
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Render-time placeholder probe (issue #1264 precondition) PHPROBE_LINE_A: !`.github/probe-plugin/phprobe-read-env.sh` <!-- The line above is the entire measurement. Three limbs at once: (a) SUBSTITUTION — if claude-code-action renders the placeholder, `PHPROBE_LINE_A:` is followed by the script's stdout (`PHPROBE_ENV <value>`). If it does not, the raw `!`-backtick text survives verbatim and the agent echoes that back instead. (b) ENVIRONMENT — the script reads DEVFLOW_PROMPT_EXTENSION_ROOT, which the probe job sets to a sentinel via the step-level `env:`, and reports the literal token UNSET when it is absent rather than emitting an empty line. (c) ALLOWLIST GATING — ALREADY ANSWERED, NEGATIVE, and the job's grant records that answer rather than contradicting it. The head is a repo-relative script path, not `printf`. It was deliberately withheld at first, and rendering was REFUSED — run 31058504896, `This command requires approval` — so placeholder rendering IS gated by --allowed-tools. The job therefore grants `Bash(.github/probe-plugin/phprobe-read-env.sh:*)` alongside `Bash(printf:*)` and `Skill`: with (c) settled, that grant is the only thing that makes limbs (a) and (b) observable at all (four consecutive runs were refused before substitution could ever be seen). Do not "restore" the withheld form — it re-measures a settled limb and blinds the two that are still open. WHY THE COMMAND IS...

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

AI & Automation Listed

probe

How to run the test-plugin probe and read its report — which field verifies which part of the docs/262 plugin usage contract.

7 Updated today
nikzlabs
AI & Automation Listed

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.

0 Updated 1 months ago
relusion
AI & Automation Listed

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.

1 Updated 3 weeks ago
serhiy-bzhezytskyy