pr flow

Engineering Community

Skill notes

Argus Behavior Model

Understand these Argus capabilities before executing: Fix-detection resolve (B-1): Argus compares new commit diff against open threads by file+line. If code at the thread location changed, Argus auto-resolves the thread. New findings block APPROVE (A): If the current review iteration produces ANY new findings, Argus returns COMMENT, not APPROVE. APPROVE only happens when: zero new findings AND all threads resolved.

Phase 1: Create PR

MANDATORY: Push branch, then create PR with metadata. GATE 1: PR created. Extract and store PR_NUMBER and PR_URL.

Phase 2: Poll for Initial Review

MANDATORY: Create a CronCreate job to poll. Do NOT use sleep loops. Review polling field selection (see #190) Use reviewDecision as the authoritative approval gate — it reflects GitHub's own per-reviewer-latest aggregation and flips to APPROVED only when all requested reviews are satisfied. Always include state in the JSON query so polling can stop cleanly on MERGED / CLOSED / DRAFT transitions. A cron that ignores state will keep polling a closed PR until it hits the quiet-check timeout, producing false alarms.

Phase 3: Read + Triage ALL Findings

MANDATORY: Read every finding before fixing anything.

Step 3c: Parse Argus comment format

Each inline comment has this structure: <suggested fix> <ready-to-apply code> In file <path> around lines <N>-<N>: <machine-readable description>

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview pr-flow.preview
# Step 5c: Process incremental review result

ITERATION=$((ITERATION + 1))
if [ "$ITERATION" -ge "$MAX_ITERATIONS" ]; then
  echo "Max iterations reached. Requesting human intervention."
  gh pr comment "$PR_NUMBER" --body "Max review iterations ($MAX_ITERATIONS) reached. Requesting human guidance."
  # STOP — do not continue
fi

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.