GitHub PR Comment Commands

Manual `/omar ...` commands for baseline refresh, deep scan, full-depth, fix-plan, and report.

  • github
  • pr-comments
  • commands

Use PR comment commands when you want deeper audits beyond the default Omar Gate check run.

Command table

| PR Comment | Purpose |

|---|---|

| `/omar baseline` | Refresh baseline memory/context. |

| `/omar deep-scan` | Standard deep audit pass for changed and related scope. |

| `/omar full-depth` | Full-depth profile for broad persona/domain coverage. |

| `/omar fix-plan` | Generate remediation plan package from current findings. |

| `/omar report` | Publish dashboard-linked report package for HITL/review handoff. |

Trigger with GitHub CLI


gh pr comment <pr-number> --body "/omar deep-scan"

gh pr comment <pr-number> --body "/omar fix-plan"

Expected progression

  1. PR receives command acknowledgement.
  2. New run appears in dashboard with timeline + artifacts.
  3. Findings and/or plan outputs are posted back to PR and available in artifacts.

Structured Answers

Do these commands replace Omar Gate branch protection?

No. Keep Omar Gate as the required merge gate; use comment commands for optional deeper investigation.

Which command should I run first after a blocked gate?

Start with /omar deep-scan. Move to /omar full-depth when policy requires broader domain coverage.