status

Display workflow enforcement state from .workflow/state.json for the active branch.

5|1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill status-joshsmithxrm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/joshsmithxrm/power-platform-developer-suite/tree/main/.claude/skills/status
Command: npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill status-joshsmithxrm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Display the current workflow enforcement state for the active branch.

Core Features & Use Cases

  • Reads the repository's workflow state from .workflow/state.json.
  • Reports gates, extension, TUI, MCP, CLI, QA, Review, and PR status with clear indicators.
  • Handles missing state files gracefully and outputs guidance when no state is tracked.

Quick Start

Run /status to display the current workflow enforcement state for the active branch.

Frequently Asked Questions about status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my branch workflow status and PR readiness?

You can check branch workflow status by running a command that reads the .workflow/state.json file to audit verification gates, QA, and PR readiness. It displays per-surface enforcement states with clear indicators.

What happens when workflow state is missing from a repository?

When workflow state is missing, the system handles the missing state file gracefully and outputs guidance indicating no state is currently tracked for the active branch.

How do I audit pipeline gates and verification statuses across repositories?

Auditing pipeline gates involves reading the repository's workflow state file to report extension, TUI, MCP, CLI, QA, Review, and PR statuses with clear indicators and staleness checks.

Does workflow status reporting require any specific dependencies or components?

Workflow status reporting requires no external dependencies or components. It solely relies on reading a .workflow/state.json file present in the repository to display the enforcement state.

Can I see staleness checks for per-surface verification states?

Staleness checks are included in the formatted output alongside per-surface verification statuses, ensuring you see current gate, QA, and PR readiness conditions for the active branch.