Menu
Launch an independent Pi CI monitor after an eligible Git event or user request.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
SDD-mode PR-boundary review policy for Pi. The root launches visible reviewer lanes, publishes triage, ends the turn for acknowledgement, then fixes in a separate follow-up. Review is independent of CI.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Create a pull request with review, REQ backlinks, push, and CI handoff.
Verify a deployed UI in a browser for interaction, mobile layout, and visuals.
Workflow for /sdd clean — rescuing a rotted spec. Mode-aware behaviors (interactive/auto/unleashed), safety nets, what gets cleaned (incl. per-AC @impl AND @test anchor backfill at parity, gated by enforce_tdd), JUDGMENT auto-resolution rules. Invoked when /sdd clean runs. Requires the spec-driven-development skill for REQ format and Status semantics, and the spec-enforce skill family for the detection mechanics.
| name | ci-monitoring |
| description | Launch an independent Pi CI monitor after an eligible Git event or user request. |
| version | 2.0.0 |
The Pi PR-boundary extension is the sole automatic dispatcher. Run this resolver only when its launch plan includes a CI wave (or when the user explicitly requests monitoring). Issue every reviewer call in the plan first, then run the resolver once without waiting for reviewer completion:
node ~/.pi/agent/skills/ci-monitoring/scripts/monitor-ci.mjs request event=<push|pr-create> changed=true repo=<owner/repo> pr=<affected-pr-number> cwd=<absolute-repo-root> reviewState=<launched|not-required>
The explicit repository, affected PR number, and cwd bind lookup to the boundary's exact PR independently of the session's starting directory or checked-out branch. The review state keeps CI last in launch order without coupling its execution or result to review. No stdout means no action. Otherwise parse the single JSON object and submit it exactly once to the public subagent tool without changing any field. It launches ci-monitor in the background with no inherited conversation and no agent turn cap; the attached script timeout bounds execution.
An explicit user request may also launch ci-monitor for a known open PR using this exact prompt:
repo=<owner/repo> pr=<number> head=<full headRefOid>
The dedicated agent runs the seeded monitor script once. Its native completion begins with exactly one of CI_RESULT success, CI_RESULT failure, or CI_RESULT timeout. Monitoring stays outside the main session. The agent only reports; the main session owns any follow-up changes.
Do not infer another automatic trigger from the Git command itself. If a task is interrupted, wait for a later extension-issued boundary plan or explicit user request rather than relaunching it automatically.