skills.rest
diazMelgarejo
diazMelgarejoCOMMUNITY
Explore all skills by this author →
Website𝕏@Melgarejo_yDiazGitHub

pt-orama-review

Reviews PT-orama plans, branches, diffs, and handoff packages with findings-first critique.

Updated Mar 22, 2026
Search Tags:#code review#verification#handoff#windows#plan review#hermes#findings-first
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill pt-orama-review-diazmelgarejo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pt-orama-review
Source: https://github.com/diazMelgarejo/orama-system/tree/main/bin/orama-system/skills/hermes-harness/commands/pt-orama-review
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill pt-orama-review-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing PT-orama plans, branches, diffs, and handoff packages manually risks missing P0/P1 defects, false claims about tools or commits, and Windows readiness gaps. This Skill enforces a strict, evidence-first review process with a consistent output structure. ## Core Features & Use Cases - Findings-First Critique: Prioritizes P0/P1 defects, security risks, bad assumptions, and broken verification before anything else. - Harness-Readiness Checks: Validates Windows readiness items including the Hermes launcher path, HERMES_GIT_BASH_PATH, LM Studio chat canary, and AGY install and output canaries. - Structured Review Output: Produces a fixed FINDINGS / OPEN QUESTIONS / VERIFICATION NEEDED / APPROVAL report ending in CLEAN or NEEDS_REVISION. - Use Case: Before merging a PT-orama branch, run this review to catch duplicated canonical knowledge, stale links, mojibake, and absolute workstation paths in tracked content. ## Quick Start Ask the assistant to run pt-orama-review on your current PT-orama branch or handoff package and return a findings-first report.

Frequently Asked Questions about pt-orama-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a PT-orama plan or branch before merging?▼

Invoke the pt-orama-review command against the plan, branch, diff, or handoff package. It returns a findings-first report listing severity-tagged issues with evidence and fixes, ending in a CLEAN or NEEDS_REVISION verdict.

What does a findings-first code review check for?▼

It prioritizes P0/P1 defects, security risks, bad assumptions, and broken verification. It also flags false claims about installed tools, models, branches, commits, or PRs, plus missing tests and stale links.

Does this review work on Windows with Hermes?▼

Yes, it is compatible with Hermes, Codex, and Windows. It specifically checks Windows readiness gaps such as the Hermes launcher path, HERMES_GIT_BASH_PATH, LM Studio chat canary, and AGY install and output canaries.

Will the review rewrite or commit my code automatically?▼

No. The review only reports findings, open questions, and verification needs. It does not rewrite your work unless explicitly asked and never commits changes.

What output format does the review produce?▼

It produces a fixed structure: FINDINGS with severity, path, issue, evidence, and fix; then OPEN QUESTIONS, VERIFICATION NEEDED, and an APPROVAL line marked CLEAN or NEEDS_REVISION.

Related Skills

Explore More Software Engineering Skills→
kellymearskellymears

git:pr

Creates GitHub pull requests with conventional commit titles and structured bodies.

Community
Intermediate
MattVOLTAMattVOLTA
4

cleanup-branches

Automate cleanup of stale local Git branches and orphaned worktrees.

Community
Advanced
SirTheOracleSirTheOracle

adversarial-verify

Re-run QA manifest findings and generate a verification-report.yaml with pixel-diff evidence.

Official
Advanced
skaile-aiskaile-ai

gh-create-pr

Open a draft GitHub pull request from the current feature branch using the gh CLI.

Official
Intermediate