Menu
Use when: reviewing OSS pull requests against review standards, comment etiquette, and contribution gate criteria.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when: reviewing .prompt.md, .agent.md, SKILL.md, or .instructions.md files for contradictions, ambiguity, persona consistency, cognitive load, coverage gaps, and composition conflicts.
Use when: checking xanadAssistant workspace health, install status, repair reasons, or lockfile validity before proposing install, update, repair, or restore operations.
Use when: designing or reviewing CI/CD pipelines, GitHub Actions, stage design, environment gates, or artifact discipline.
Use when: writing or reviewing Dockerfiles, container images, multi-stage builds, layer caching, or image security.
Use when: writing or reviewing Infrastructure as Code for naming, state management, modularity, and drift detection.
Use when: reviewing DevOps changes for pipeline safety, secret hygiene, permissions, rollback, and deployment risk.
| name | ossCodeReview |
| description | Use when: reviewing OSS pull requests against review standards, comment etiquette, and contribution gate criteria. |
| type | reference |
| version | 1.0 |
| license | MIT |
Skill metadata: version "1.0"; tags [oss, code-review, pr]; recommended tools [].
Use this skill when reviewing OSS pull requests or when a maintainer needs structured guidance on what to check before merging.
secureReviewdocsReviewRun through all tiers before leaving a verdict.
| Tier | What to check | Block merge? |
|---|---|---|
| Correctness | Logic is sound; edge cases handled; no regressions | Yes |
| Tests | New behavior has tests; tests actually fail before the fix | Yes |
| API compatibility | No unannounced breaking changes to public surface | Yes |
| Documentation | Public API changes are documented; changelog entry present | Yes if API changed |
| License & DCO | Repository-specific license obligations are met; DCO sign-off present if required | Yes if required |
| Security | No new injection vectors, hardcoded secrets, or insecure defaults | Yes |
| Style | Matches project conventions; linter clean | Suggest only |
| Performance | No obvious O(n²) regressions in hot paths | Suggest only |
Use the following prefixes to make severity obvious:
| Prefix | Meaning |
|---|---|
nit: | Non-blocking style preference |
suggest: | Non-blocking improvement idea |
question: | Clarification needed; may block if unanswered |
request: | Change required before merge |
blocker: | Must-fix; do not merge until resolved |
Example:
blocker: This is vulnerable to SQL injection — use a parameterized query.
suggest: Consider extracting this loop into a named helper for readability.
nit: Trailing whitespace on line 42.
A PR is ready to merge when:
request: or blocker: comments.## [Unreleased] (for user-visible changes).