sflow-report

Generate a read-only Singularity Flow workflow performance report with phase duration, approval waiting, rework, committed model/token telemetry, provider or configured cost, and bottlenecks.

SKILL.md

GitHub

Report workflow performance

<!-- sflow-copilot-pause -->

Before any boundary lookup or SFlow action, run singularity-flow pause status --json and follow its data.agentInstruction. If data.paused, answer as native Copilot, only offer /sf-pause off and never resume implicitly.

<!-- sflow-output-contract: concise-relay -->

Output contract: Relay requested CLI fields or output faithfully; preserve warnings/errors and only the explanations required below. Summarize artifacts with verified Markdown-preview links; never paste document bodies, code or diffs into Copilot. For code, list touched paths and observed added/deleted/created line counts; unavailable stays unavailable. Use existing evidence, not extra calls solely for display. Summaries, links and opened previews are not human review or approval. For every next action, honor returned commandGuidance in order: Copilot, Shell, VS Code (model-free) using modelFreeCommand; if absent, say "not available for this action". Missing Copilot: "no verified equivalent". Never invent routes.

<!-- sflow-execution-boundary -->

Boundary: no Story required; cwd=opened Git root or verified repositoryPath from singularity-flow workspace current --json; refuse if neither resolves; never search $HOME/parents. Use exact CLI-returned paths. repositoryPath is command cwd, not a prefix for absolute file paths. Never rebase paths or strip .git/worktrees. Issued private/external files are exact exceptions to repository confinement, not wider read/write permission; writes still need authorization. Resolve relative paths only against their declared base. On failure, preserve the path and error; never search or recreate it.

  1. Run singularity-flow report <arguments>.
  2. Summarize elapsed wall-clock time, active time, approval waiting, generations, rejections, self-approvals, token availability, and the approval-latency bottleneck.
  3. Read committed telemetry/ references returned by the CLI under immutable workflow.resolution.workItemRoot; never assume singularity/work-items. Treat token totals as exact only where the provider supplied exact usage. Preserve partial and unavailable disclosures.
  4. Summarize the Copilot activity section, which stands in when tokens are unavailable: requests sent, turns, tool calls, estimated premium requests (requests × tokens.premiumMultipliers; GitHub's billing is authoritative), quota or model-substitution events, and the governed prompt's size against its budget. Keep estimated, partial and unavailable; a missing count is never zero.
  5. Prefer exact provider cost captured by Copilot OTel. Otherwise show cost only when workflow YAML contains pricing for the exact recorded model; explain that configured prices are per million tokens and may be partial.
  6. Explain that durations include nights and weekends and are not business-hours or productivity estimates.
  7. Do not change workflow state, generate artifacts, submit, approve, reject, commit, or push. Only write a report file when the user explicitly supplies --out.