// Pre-merge review checklist based on recurring AI reviewer feedback patterns
Helps users delegate tasks, break them into steps, set deadlines, and track progress via routines and memory.
Suggests relevant cron routines based on user context, goals, and observed patterns
Install and operate a full GitHub issue-to-merge workflow in Steward using event-driven and cron routines. Use when setting up or tuning autonomous project orchestration: issue intake, planning, maintainer feedback handling, branch/PR execution, CI/comment follow-up, batched staging review every 8 hours, and memory updates from merge outcomes.
Build, run, and test Steward locally using Docker containers and Chrome MCP browser automation.
Test the Steward web UI using the Claude for Chrome browser extension.
| name | review-checklist |
| version | 0.1.0 |
| description | Pre-merge review checklist based on recurring AI reviewer feedback patterns |
| activation | {"patterns":["review.*checklist","ready to merge","pre-merge check","check.*before.*merge"],"keywords":["review","checklist","merge","pre-merge"],"max_context_tokens":1500} |
Before merging, verify these items. They represent the most common issues caught by automated code reviewers (Copilot, Gemini) on Steward PRs.
redact_params() before logging or SSE/WebSocket broadcastrequires_approval() returning Always or UnlessAutoApproved&s[..n]) on external/user strings -- use is_char_boundary() or char_indices().to_ascii_lowercase() before matching)LlmProvider trait methods are delegated in ALL wrapper types (grep impl LlmProvider for)tempfile crate, no hardcoded /tmp/ pathsserial_test)