devpowers

Create, comment on, or update the description of Jira tickets in your configured project with structured descriptions. Use when the user wants to open, create, or file a Jira ticket, bug, task, or story, OR add a technical comment to an existing ticket, OR rewrite an existing ticket's description. Triggers on: "/jira-ticket", "open a jira ticket", "create a jira bug", "file a task", "comment on PROJ-1234", or any request to create/comment on a Jira issue. Three modes: create (default), comment (issue key given), and update-description (issue key + "description"). Examples: "/jira-ticket bug, current", "/jira-ticket PROJ-1234", "/jira-ticket PROJ-1234, description". Requires the jira-setup skill to have been run first; if env vars are missing this skill will invoke jira-setup automatically.

Run the project's existing Playwright tests and bundle their screenshots into a single self-contained `index.html`. Use when the user asks for an e2e screenshot report, a visual record of UI flows, a PR-ready visual of the running app, or invokes `/screenshots`. Playwright-only.

Review and shorten markdown docs, code comments, and docstrings — cut wordiness, redundancy, and code duplication. TRIGGER on .md file edits inside subdirectories, or when user asks to shorten/condense docs, comments, or docstrings. Skip root-level .md files (CLAUDE.md, README.md, CHANGELOG.md, etc.).

Ensure the mcp-atlassian MCP server is registered and resolve Jira defaults (URL, auth, project, board) so the jira-ticket skill has everything it needs. Idempotent — re-runs only prompt for whatever is missing. Use when the user wants to set up or reconfigure Jira, install / register mcp-atlassian, pick a default project or board, or persist Jira env vars to their shell rc. Also invoked automatically by the jira-ticket skill when required env vars are missing. Triggers on: "/jira-setup", "set up jira", "configure jira", "install mcp-atlassian", "pick jira project", "pick jira board".

Check the latest GitHub Actions workflow run result through the GitHub MCP server's actions toolset (no gh CLI). Use when the user asks to check, inspect, or view the status of a workflow run (e.g. "/action-check pypi publish", "/action-check test"). Uses the github MCP server bundled with this plugin (requires GH_TOKEN).

Trigger and monitor any GitHub Actions workflow through the GitHub MCP server's actions toolset (no gh CLI). Use when the user asks to run, trigger, or execute a GitHub Action (e.g. "/action-run pypi publish", "/action-run generate migration"). Uses the github MCP server bundled with this plugin (requires GH_TOKEN).

After a git push, find the PR for the current branch, watch CI checks through to completion via the GitHub MCP server, and surface unresolved review comments. On failure, report the failed checks with their run URLs so they can be triaged. Use after every git push, or when the user asks to check PR / CI / review status (e.g. "/check-pr", "/check-pr --comments-only", "check the PR", "is CI green?"). Uses the github MCP server bundled with this plugin (requires GH_TOKEN).

Register a known MCP server in this project or in the user's Claude Code config. Bounded to the curated list in ./mcps.json — will not install MCPs that aren't in the manifest. Use when the user wants to install, add, configure, or register an MCP server (e.g. "/setup-mcp", "/setup-mcp github", "set up the atlassian mcp", "install mcp-atlassian"). Also invoked by other skills when their required MCP isn't available in the session.

Debug Docker containers running locally. Use when the user wants to discover running containers, tail local docker logs, or troubleshoot services running on this machine. Triggers on mentions of "local docker logs", "tail container logs", "what's running locally", "docker debug", or debugging containers on the local Docker daemon.

Debug Docker containers running on a remote VM via SSH. Use when the user wants to discover running containers, tail remote docker logs, or troubleshoot deployed services on a remote host. Triggers on mentions of "remote docker logs", "prod debug", "tail container logs", "what's running on <host>", or debugging containers on a deployed VM.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Create a git commit with staged changes, handling pre-commit hooks automatically. Use when the user asks to commit, make a commit, or create a commit (e.g. "/git-commit", "/git-commit fix login bug").