polypoint-skills

Gated, sub-agent-driven PR review for Azure DevOps. Verifies the repo, redacts PII, fans out parallel analyses (core logic, tests, security, SQL/JPA, memory, performance, and POLYPOINT Coding Guidelines), triages findings with the developer into a curated set, then drafts and posts PR comments only on explicit confirmation.

11 skills · 1 command · hooks

Babysit an Azure DevOps pull request for a time window — watch for new review comments (CodeRabbit and human) and CI state changes via the az CLI, verify each finding against current code, fix still-valid issues minimally, resolve bot threads, draft replies to human threads for approval, and diagnose failing builds. On draft PRs asks right away whether to kick-start CodeRabbit and the build policies, marks every posted comment as AI-generated, and can run in a linked worktree so the main checkout stays free.

1 skill

Plan, orchestrate and review POLYPOINT cloud production release nights with the release board of the pcr-companion repo — scope from the Confluence release page plus the release-branch diff, the plan built with sections, tasks and deploy groups (a component from release/preview or release/maintenance, an existing Azure DevOps release or a new one), window order and downtime estimate, next-step guidance and failure diagnosis on the night (the operator runs every step), retro with tested fixes, the plan's changed and new steps brought back into the catalogue through one PR, and archived evidence.

1 skill

Guide the conversion of Polypoint P2 Delphi VCL forms (.dfm/.pas) and frames into Angular standalone components — analyzing DFM/PAS sources, mapping VCL components to Angular + @pdx/* equivalents, extracting business rules into rule cards enforced in the MSW handlers handed to the backend team, and emitting PDX-styled features with NgRx Signal Store and Signal Forms.

1 skill

Performs a short, structured design review of a single design-system component against its Figma source — checking visual fidelity, states, accessibility, and implementation consistency from a developer's perspective. Includes a POLYPOINT/PDX-specific addendum. Not for full-page or layout reviews.

1 skill

End-to-end Jira ticket development workflow — fetch the ticket from Jira, deep analysis with an approved summary, reproduce the bug first, implement in an isolated git worktree, verify live together with the user (headed browser, shared test environment, hand-over test), logically-grouped commits + push, PR creation marked as Claude-generated, then babysit the PR to merge. Project-agnostic: derives project context from the repo, asks for the rest, and remembers it in memory per project (/dev-ticket setup for a guided first run).

1 skill

Reflect on how the skills used in the current session performed and upload concrete HTML improvement plans to Whetstone for asynchronous human review — run /improve after any skill-driven task instead of baking a self-improvement section into every skill.

1 skill

Apply the PDX (POLYPOINT Design Experience) design system to Angular frontends — installing and using @pdx/* libraries, replacing Angular Material with PDX equivalents, applying design tokens and typography, building forms with pp-form, and auditing existing UI for PDX consistency.

1 skill

Drive and verify things directly in PEP (POLYPOINT's Delphi/VCL personnel-planning Windows client) on a tenant box over RDP/SSH/WinRM — element-level automation (pywinauto over a loopback agent), not pixel clicking. Runs a preflight check, bootstraps the companion pep-driver toolchain, then runs selector-based UI commands and flows.

1 skill

Create Playwright API tests based on a playwright e2e test, it will test the corner cases missed by the e2e test

1 skill

Create Playwright E2E tests using Chrome browser exploration for real selector discovery and Page Object Model patterns

1 skill

Deeply investigate a codebase topic and produce a structured research document with architecture diagrams, glossary, and actionable findings

1 skill

Guided end-to-end implementation of Zn2C Quick-Win issues from the ZQW Jira board

1 skill