smoke-gate-runner
Skill1 starsChanged 9 months agoMITView on GitHub
Run project-wide smoke commands and write deterministic gate evidence artifacts for Conflux tracks. Use when preparing completion gates, validating regressions, or producing planning/project_smoke_report.json and planning/red_green_report.json.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- chaos-fuzz-runnerSkill
- data-migration-safetySkill
- external-integration-reliabilitySkill
- failure-forensicsSkill
- harmonization-operatorSkill
- hud-control-opsSkill
- mcp-policy-opsSkill
- search-index-tuningSkill
- sync-conflict-playbookSkill
- track-contract-authorSkill
- transaction-concurrency-guardSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 8
Use this skill to generate non-blocking quality gate evidence for a track.
- Distinctive: line 12
Run smoke checks and write report:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Smoke Gate Runner
Use this skill to generate non-blocking quality gate evidence for a track.
Workflow
- Run smoke checks and write report:
scripts/run_smoke_gate.py --track-path conductor/tracks/<track> --cmd "pytest -q tests/smoke"
- Optionally produce red/green report:
scripts/run_red_green_gate.py --track-path conductor/tracks/<track> --red-cmd "<expected fail command>" --green-cmd "<expected pass command>"
- Feed resulting JSON reports into normal Conflux gates.
Notes
- Reports are written to the track
planning/folder. - This skill does not block orchestration by itself.
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.