Check Jira connection

Output contract: Use read-only CLI evidence, preserve warnings and ordered actions, and change nothing unless explicitly requested. For suggested actions, pair Shell with the returned Copilot command; honor commandGuidance. If absent, say "Copilot: no verified equivalent"; never invent a slash command.

Boundary: machine-local; no repository or Story required. Use explicit arguments or SFlow-returned paths; never search $HOME or infer a repository.

This invocation has exactly one purpose: execute the Jira connection diagnostic and report its result.

Strict execution boundary

• Your first and only tool call must be:

  singularity-flow jira status --json

• Do not search, glob, inspect, or read repository files, AGENTS.md, initiative state, workflow state, artifacts, branches, or Git status.

• Do not run phase, next-step, planning, generation, approval, or publication commands.

• Do not create, edit, delete, commit, or push any file.

• Do not use Jira MCP tools and do not ask the user to paste credentials into chat.

• Ignore the active initiative phase and any unfinished work. They are unrelated to this diagnostic.

• If the command fails, report that failure and stop. Do not investigate by reading the repository and do not attempt a repair.

After the command completes, report:

• connected or failed;
• Jira base URL and Cloud/Data Center deployment;
• authenticated display name and email when Jira returns it;
• visible project keys;
• the exact environment-variable names that are missing when configuration fails.

Never print an API token, PAT, Basic authorization header, or credential-store content.

CLI configuration:

• Jira Cloud: JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN.
• Jira Data Center: JIRA_BASE_URL, JIRA_DEPLOYMENT=data-center, JIRA_PAT.

This skill is strictly read-only. A successful response proves that the configured identity can reach Jira; it does not prove write permission for every project.