Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

hansjm10

@hansjm10 source repo

8 published skills

  1. ▌
    Pr Audit · hansjm10
    Audit a PR review for false positives, scope drift, overstated claims, and unsubstantiated assertions. Use when: (1) User runs `/pr-audit`, (2) User asks to "audit" or "check" a review, (3) User wants to find false positives or verify claims in a review, (4) User provides a review and asks if claims are justified. Does NOT re-review the PR; evaluates whether the review's claims are supported by evidence.
    0 installs
  2. ▌
    Pr Review · hansjm10 bundle
    Orchestrated PR review workflow producing evidence-based, audited technical reviews. Use when: (1) User requests a PR review with `/pr-review`, (2) User provides a PR URL or reference like `owner/repo#123`, (3) User asks for a "full review" or "technical review" of a pull request. Default output is a human-readable Markdown review + a short plain-text summary (no XML). Use `--show-xml` to also emit XML artifacts for each phase (retrieval_plan, evidence_pack, requirements_pack, draft_review, audit_report, final_review, comment_posted).
    0 installs
  3. ▌
    Sonarqube · hansjm10
    Access SonarQube or SonarCloud issues and quality gate data via API using tokens. Use when fetching PR/branch issue lists, leak-period problems, or quality gate status for a project.
    0 installs
  4. ▌
    Pr Evidence · hansjm10
    Extract factual evidence from a PR diff without interpretation or judgment. Use when: (1) User runs `/pr-evidence`, (2) User asks to "extract evidence" from a PR, (3) User wants a facts-only summary of PR changes, (4) User provides a PR reference and asks what changed without asking for review/opinions. Produces an evidence_pack XML artifact with changed files, code changes, design decisions, tests, and docs.
    0 installs
  5. ▌
    Pr Requirements · hansjm10
    Extract acceptance criteria and requirements from a GitHub issue. Use when: (1) User runs `/pr-requirements`, (2) User asks to "extract requirements" from an issue, (3) User wants to know what a PR should accomplish based on its linked issue, (4) User provides an issue URL and asks what the acceptance criteria are. Produces a requirements_pack XML artifact with acceptance criteria, constraints, and ambiguities.
    0 installs
  6. ▌
    Pr Review Comment · hansjm10 bundle
    Convert <final_review> XML from the pr-review workflow into a human-readable Markdown comment and post it to GitHub via gh. Use when: (1) the orchestrator or user requests `/pr-review-comment`, (2) a non-XML PR review comment must be published from a <final_review> payload, or (3) a follow-up step needs to post review results directly to a PR.
    0 installs
  7. ▌
    Pr Review Summary · hansjm10
    Produce a short, human-readable, non-XML summary from a <final_review> XML artifact. Use when: (1) a pr-review workflow completes, (2) a user asks for a brief PR review summary without XML, (3) an orchestrator needs a plain-text recap of review outcomes.
    0 installs
  8. ▌
    Shell Desktop MCP · hansjm10 bundle
    Operate the Idle Engine Electron shell through the shell-desktop MCP server, including deterministic simulation control, renderer/log/WebGPU diagnostics, window screenshots, shell input events, and compiled asset inspection. Use when tasks mention shell-desktop MCP, Electron shell automation, runtime debugging, or regression capture from desktop shell behavior.
    0 installs