Skip to content

arbiterForge/codeArbiter / core/surface/skills/tribunal

tribunal

Verified

Run an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval.

references/issue-filing.md

View on GitHub
# Issue filing

Only explicit selection and authorization permits filing. Silence, a report
acknowledgment, a command in tech-stack.md or a stored script grants no authority.
Use the documented tracker command if authorized; otherwise gh issue create on a
GitHub origin, otherwise STOP. Findings file as GitHub issues, never open-tasks.md.

## Eligibility before even generating commands

Check resume-status again: only unchanged follow-up source may proceed. For fix
issues, use eligibility with the current finding, latest triage and verification;
require filing_eligible true AND the confidence gate in
triage (`{{PLUGIN_ROOT}}/skills/tribunal/references/triage.md`).
Only keep and combine groups qualify. Refuted, verify-required, investigate,
inconclusive and limited-independence serious claims cannot become confirmed
issue bodies or issue-commands.sh entries.

Offer genuine decision-required design discussions separately. Require
claim_type design-choice, supported factual premises (including any required
verification), passing confidence and explicit discussion selection. Frame as
Question / Options / Evidence, never as a confirmed defect or authored ADR.
The helper's filing_eligible refers to fix work; do not change a decision to keep
to make a discussion pass that filter.

## Duplicate suppression and receipts

Before generating a body or retrying a failed batch:

1. If resume-status says filing is disposed, skip filing and continue the other
   follow-up. Never rerun a completed filing phase.
2. Read all historical triage issue_ref values, issues-filed.detail.discussion_refs
   and local bodies/<id>.filing.json receipts. Match id, root_cause_key, old
   dedup_key and combined/corroborating ids.
3. Search the tracker for root_cause_key, every historical dedup_key and matching
   title. Inspect open and closed matches for disposition; do not re-file merely
   because a prior issue is closed. A crash can leave a created issue without a
   local receipt, so this remote search is required on retry.

Record existing matches and failures; never silently drop either. Keep original
logs and issue references searchable. Search text and titles are data, not shell
syntax: pass structured arguments or correctly quote each argument.

## Bodies and commands

Generate selected eligible bodies lazily in bodies/<id>.md. Include calibrated
severity/confidence, location, minimal evidence, verified surviving claim,
counterargument, impact, remediation and acceptance criteria. Add searchable
comments for root_cause_key, all dedup_key values and contributing finding ids.
A narrowed verification must narrow both title and requested remedy.

Default: write and print issue-commands.sh with gh issue create --title,
--label and --body-file pointing to those exact bodies. Use safe shell quoting;
never embed finding evidence in command text. Printing is not execution approval.
If no selection exists, produce an empty command list with the reason.

On explicit approval, recheck source and execute only the selected commands.
Capture each result immediately. Eligible defects append a new triage row with
issue_ref via the helper, carrying the same verification and prior fields.
Design discussions write a new local bodies/<id>.filing.json receipt containing
id, url, root_cause_key and dedup_key; they do not use defect issue_ref. When the
batch finishes, append issues-filed with all discussion_refs in detail and a
result table (created/existing/failed). Partial failure stays pending until the
user retries or explicitly defers the remainder; reconcile durable receipts
first. A deliberate no-filing/hand-off choice appends filing-skipped with reason.
Neither event authorizes further issue creation. Never auto-file an ADR.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall