Review code diffs for correctness, regression, and architecture conformance.
npx skills add https://github.com/RhyTsui/PMOS --skill pmos-code-review
Please help me install this Agent Skill. Skill: pmos-code-review Source: https://github.com/RhyTsui/PMOS/tree/main/skills/pmos-code-review Command: npx skills add https://github.com/RhyTsui/PMOS --skill pmos-code-review
It prevents unsafe or incorrect implementation changes from slipping past the acceptance gate by enforcing a structured, incremental review focused on correctness, regressions, architecture conformance, and requirement traceability.
Use the skill for a pre-acceptance review of the current change set by asking it to triage findings into blocker and should-fix items and state whether testing acceptance may proceed.
High-intent search queries and answers about installing and using this skill.
Pre-acceptance code review analyzes an incremental diff to check correctness, regression risk, architecture conformance, and requirement traceability. It triages findings into blockers, should-fix items, and residual risks to determine if the change set can pass testing acceptance.
Requirements traceability in governed code review verifies that incremental implementation changes align with specified requirements. It identifies requirement mismatches within the change set to prevent incorrect or unsafe code from slipping past the acceptance gate before testing closes.
Test-gap analysis and regression prevention identify missing tests and behavioral regression risks by reviewing the actual code diff. This incremental review categorizes these risks as blockers or should-fix items, producing a clear rework recommendation to stop unsafe changes at the acceptance gate.
Yes, incremental code review checks architecture conformance by evaluating the actual diff for architecture drift. It scopes the review to the current change set rather than historical debt, categorizing any architecture violations as blockers or should-fix items before testing acceptance.
The best way to triage findings for acceptance gating is to categorize them into explicit blocker, should-fix, and optional follow-up levels. This governed review produces scoped outcomes with clear pass or rework recommendations, ensuring only safe changes proceed past the acceptance gate.
Code review for regression prevention reviews only the actual incremental diff. This change-set-first approach keeps the review governed and focused on the current changes, avoiding historical debt while performing correctness and traceability checks before testing acceptance.
dfmonacoRequest a focused code review with diff range and requirements.
CoachSteffPlan and execute unit, integration, E2E, and UAT testing strategies.
trevorbyrumGenerate unit tests for source code based on identified testing gaps.
johinsDevStandardize environment variable and secret management across deployments using Infisical.
