<< All versions

Skill v1.0.1

currentLLM-judged scan90/100
ashokraj2011/singularityflow/sflow-jira-doctor

+1 new

──Details
PublishedOctober 21, 2026 at 08:15 PM
Content Hashsha256:30740e0a116b42aa...
Git SHA12bda1160dd0
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 2.9 KB)
SKILL.md2.9 KBactive
SKILL.md · 44 lines · 2.9 KB

version: "1.0.1" name: sflow-jira-doctor description: Diagnose the active Singularity workspace Jira policy, CLI credentials, connection, project permissions, boards, and Epic visibility without changing Jira, Git, or repository files. disable-model-invocation: true


Diagnose Jira configuration

<!-- 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: guided-actions --> Output contract: Use read-only CLI evidence, preserve warnings and ordered actions, and change nothing unless explicitly requested. 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: machine-local; no repository or Story required. Use explicit arguments or SFlow-returned paths; never search $HOME or infer a repository. 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.

This invocation is a strictly read-only Jira diagnostic.

Strict execution boundary

  • Your first and only tool call must be:

singularity-flow jira doctor --json

  • Do not search, glob, inspect, or read repository files yourself.
  • Do not run workflow, phase, generation, approval, Jira update, Git commit, or Git push commands.
  • Do not create, edit, or delete files.
  • If the command exits with attention required, report its checks and next actions exactly; do not attempt repairs.
  • Never display API tokens, PATs, authorization headers, or encrypted credential-store content.

Summarize:

  • active workspace and selected repository;
  • repository Jira policy and write mode;
  • CLI credential availability, naming only missing variables;
  • authenticated Jira identity and deployment;
  • configured project visibility;
  • permission, board, and Epic discovery;
  • each recommended corrective action.

Explain that VS Code SecretStorage values are supplied only to commands launched by the extension. A separate terminal needs its own Jira environment variables.

← v1.0.0All versions