draft-pr-commentsTurn the developer's accepted review findings into well-formed, postable PR comments for Azure DevOps. Reads only the curated accepted-findings file. Runs as a non-interactive sub-agent producing the draft; the orchestrator presents it and applies edits. Use after triage, before the posting gate.
pp-pr-reviewUse when reviewing an Azure DevOps pull request through the complete POLYPOINT workflow: repository verification, JIRA PII redaction, parallel specialist reviews, developer-led triage, cross-cutting analysis, comment drafting, and explicitly approved posting. Trigger when the user supplies or refers
redact-jiraFetch a JIRA ticket's text and produce a privacy-safe version with all personal information redacted, before that text is used anywhere else in a review. Use at the start of a PR review, after the diff is available, to prepare the ticket description for comparison against the implementation.
review-core-logicReview the core logic of a pull request against its ticket. Produces a plain-language summary, a ranked list of "review hot spots" (the most important logic, with clickable links to the code), a ticket-vs-implementation comparison, and triageable logic findings. Runs as a non-interactive sub-agent.
review-guidelinesReview a pull request against POLYPOINT's own documented Coding Guidelines — clean-code judgment rules and team-specific conventions (naming, structure, documentation) that generic linters and CodeRabbit don't know. Java/Spring backend and Angular/TS frontend. Produces a structured, non-interactive
review-memoryReview a pull request for memory problems — leaks, unbounded retention, and inefficient allocation — across Java/JVM (Spring, JPA/Hibernate), Node.js/TypeScript, and Angular (RxJS, DOM). Produces a structured, non-interactive findings report for the orchestrator to triage. Use as the memory-focused
review-openCross-cutting review step that runs after the focused steps. Connects the developer's already-accepted findings and surfaces concerns that fell between the dedicated steps (backwards-compat, operability, docs, config/migrations). Runs as a non-interactive sub-agent; the open-ended developer-directed
review-performanceReview a pull request for compute, concurrency, I/O, and rendering performance problems across Java/Spring, Node.js/TypeScript, and Angular. Excludes data-access/SQL-JPA and memory leaks (separate steps). Produces a structured, non-interactive findings report for the orchestrator to triage.
review-securityReview a pull request for security issues — injection, broken access control, auth/session flaws, secrets, XSS/CSRF/SSRF, insecure deserialization, misconfiguration — across Java/Spring, Node.js/TypeScript, and Angular. Grounded in OWASP. Produces a structured, non-interactive findings report for th
review-sql-jpaReview a pull request for inefficient SQL and JPA/Hibernate usage — N+1 queries, missing pagination, over-fetching, bad transaction/fetch strategy, missing indexes. Stays in the data-access lane (general compute performance is a separate step). Produces a structured, non-interactive findings report
review-testsReview the tests in a pull request — useless/weak tests, missing coverage for changed behaviour, and whether integration tests are warranted. Runs as a non-interactive sub-agent producing a triageable findings report. Use as the test-focused judgment step of a PR review.