// Run this skill when the user wants a guarded live Flow Healer smoke test on a real GitHub repo. Use for requests like "do a live smoke", "test this repo live", "open a real PR through the healer", or "validate issue-to-PR plumbing on GitHub".
Review a local codebase, turn validated findings into small GitHub issues, and order them by fix path. Use when the user wants a code review that produces GitHub issues instead of code changes, especially for requests like "scan this repo and create issues", "do a multi-agent review", "open fix-path issues", or "review without editing code".
Activates a structured multi-agent workflow (Team Lead + specialized Employees) to handle complex tasks that require decomposition, specialized execution, and synthesis. Use when a user request: (1) Involves multiple distinct domains (e.g., research, coding, testing), (2) Is large enough to be split into parallel sub-tasks, (3) Requires high-quality synthesis of diverse inputs. Triggers on requests like: 'Research 3 competitors...', 'Build a feature with backend/frontend/testing...', 'Analyze a business idea with market/risk/monetization agents...'
Run this skill when a Flow Healer run fails or behaves unexpectedly and the user wants a fast, deterministic diagnosis. Use for requests like "triage this healer failure", "why did the run fail", "classify this issue state", or "tell me if this is an environment problem or a product bug".
Run this skill when Flow Healer triage points to connector or patch generation failures and the user wants a deterministic connector-focused debug pass. Use for requests like "debug the connector", "why did the proposer emit no patch", "validate the verifier payload", or "compare proposer and verifier output contracts".
Run this skill when the user wants safe local validation before any live Flow Healer action. Use for requests like "run local checks", "validate the healer locally", "do a dry run first", or "make sure the repo is healthy before live GitHub actions".
Run this skill when the user wants to validate or execute a Flow Healer PR follow-up on an existing live PR. Use for requests like "rerun the same PR", "ingest review feedback", "follow up on this healer PR", or "reuse the existing issue and PR after comments".
| name | flow-healer-live-smoke |
| description | Run this skill when the user wants a guarded live Flow Healer smoke test on a real GitHub repo. Use for requests like "do a live smoke", "test this repo live", "open a real PR through the healer", or "validate issue-to-PR plumbing on GitHub". |
Use this skill for low-risk, live GitHub validation.
--repo-path--repo-slug--repo-name--output-dir--templateThe bundle generator emits a JSON object with:
templateconnector_pathconfig_pathstate_roottemplateconnector_pathconfig_pathstate_rootissue_idpr_idbranch_nameattempt_stateverifier_summarytest_summaryconnector_path and config_path exist and are ready for a guarded flow-healer start --once run.flow-healer start --once by itself.scripts/make_live_smoke_bundle.py.flow-healer start --once with the generated config..venv/bin/python skills/flow-healer-live-smoke/scripts/make_live_smoke_bundle.py \
--repo-path /absolute/path/to/repo \
--repo-slug owner/repo \
--repo-name live \
--output-dir /tmp/flow-healer-live-bundle \
--template docs_scaffold
docs_scaffold: create a minimal /docs structure from a smoke-safe issuedocs_followup_note: apply a single-file README follow-up note on an existing PR branchCapture these after the guarded flow-healer start --once run:
issue_idpr_idbranch_nameattempt_stateverifier_summarytest_summaryflow-healer start --once with the generated config only after preflight has passed and the smoke-safe issue is ready.flow-healer-triage if the live run exposes a product bug or unexpected failure.