القائمة
Run the setup interview to wire Steward to a specific project. Use when first installing the system, or when the project's repos/platforms/CI change. Produces config.yaml.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Capture issue-shaped reports that have not reached the tracker yet. Divert suspected vulnerabilities, dedupe across every surface, and stage genuinely new actionable items in the pre-tracker queue. Never files or replies on the public tracker. Watcher role, Band A.
Independently fact-check the autonomous actions the system took (issue closes, labels, capture marks, etc.) against live ground truth, and alarm on any mismatch. Run on a schedule. This is what makes Band-A public actions safe.
Triage tracker issues — initial reply under a confidence gate, label, milestone, sprint-candidate, and the dropped-ball "reporter waiting on us" surfacer. Use for ongoing issue-tracker hygiene.
Deep-review a routed PR and run the authoritative quality gate before merge. Reads the whole diff, reproduces, runs the layered gates fresh, bounces with a fix-spec or fixes mechanical blockers. Stages 3-4 of the PR lifecycle.
Screen and route an open pull request — fit/scope screen, marginal-benefit screen, and lane routing. Use at the front of the PR pipeline before any deep review. Stages 0-2 of the PR lifecycle.
Aggregate the contributor trust ledger into a shrunk-and-decayed reliability score that weights review priority and gate intensity — never a reason to skip a gate. Band A, no LLM: classification happens upstream at close, this is arithmetic over an existing event log.
| name | project-system-setup |
| description | Run the setup interview to wire Steward to a specific project. Use when first installing the system, or when the project's repos/platforms/CI change. Produces config.yaml. |
When to load: first install of the system into a project, or when something structural changes (new repo, new chat platform, new CI, new review tool).
What it does: works through the setup interview conversationally
and produces the project's config.yaml from the
template.
setup/setup-interview.md and setup/config.template.yaml. The interview is the
question script; the template is the output shape.config.yaml from the template with the collected answers. Validate it parses.config.yaml exists and parses.