devpowers

Plugin devpowers from marketplace devpowers in kolodkin/devpowers. Commands read from the repo's manifest — 3 days ago.

Skills (13)

• brainstorming

  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.

• action-check

  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 plug

• action-run

  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 (re

• ascii-sketch

  Use when a doc page, design note or chat answer needs to show a screen, panel, layout or architecture/network diagram — draws a plain-ASCII sketch that renders the same in any font.

• check-pr

  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

• jira-setup

  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,

• jira-ticket

  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. T

• local-docker-debug

  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 contai

• screenshots

  Run the project's existing Playwright tests and deliver their screenshots. Use when the user asks for an e2e screenshot report, a visual record of UI flows, a PR-ready visual of the running app, wants test screenshots shown directly in the chat, or invokes `/screenshots`. Playwright-only.

• session-review

  Full review pass over the current branch — runs code-review, simplify, ponytail-review and shortify in order. Use when the user asks for "session-review" or a full review of their change.

• setup-mcp

  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

• shortify

  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.

• ssh-docker-debug

  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>",

MCP servers (1)

• github

  connects to: https://api.githubcopilot.com/mcp/

Similar plugins