القائمة
Evaluate completed Sybra tasks — determine status transition and link PRs. Use when asked to evaluate task completion.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review what shipped in the OpenAI Codex CLI since the last adoption analysis and file an umbrella issue (☂️) + one subissue per adoptable feature, each grounded in how Sybra actually drives Codex headless. Use when asked to "check what's new in Codex", "adopt new Codex features", or to refresh the Codex CLI adoption tracker. For Claude Code, use claude-feature-adoption instead.
Fast adversarial code review. Red-teams a diff or PR to find the concrete bug, then refutes its own findings to cut false positives. Works with Claude, Codex, or Copilot — uses subagents when the runtime has them, falls back to sequential local passes. Use for routine changes where a full staff review is overkill.
Review what shipped in the OpenAI Codex CLI since the last adoption analysis and file an umbrella issue (☂️) + one subissue per adoptable feature, each grounded in how Sybra actually drives Codex headless. Use when asked to "check what's new in Codex", "adopt new Codex features", or to refresh the Codex CLI adoption tracker. For Claude Code, use claude-feature-adoption instead.
Non-interactive PR review fix — fetch unresolved review threads, auto-apply valid fixes, reply on every thread (applied/questionable/invalid). Use when given a PR URL and asked to address review feedback without prompts.
Analyze Sybra health findings + audit summary to explain workflow issues and propose grounded fixes. Use when asked to review how work is flowing or suggest process improvements.
Analyze the Sybra evaluation scorecard, breakdowns, and weaknesses, then recommend concrete improvements toward an autonomous mid-level engineering team. Use when asked how well/efficiently Sybra is working, to review the evaluation data, or to act on the fleet scorecard.
| name | sybra-evaluate |
| description | Evaluate completed Sybra tasks — determine status transition and link PRs. Use when asked to evaluate task completion. |
| allowed-tools | Bash |
| user-invocable | true |
| disable-model-invocation | true |
Decide what happens to a task after an agent finishes. Do NOT read source code, review diffs, or explore the codebase.
sybra-cli --json get <id>
Search the agent result for PR references. Look for:
gh pr create output containing a URL like https://github.com/.../pull/NIf found, link to task:
# Link PR number
sybra-cli --json update <id> --pr <number>
# Link branch if known and not already set
sybra-cli --json update <id> --branch <branch-name>
Based ONLY on the agent result text:
| Condition | New Status |
|---|---|
| Agent completed work, PR created or code pushed | in-review |
| Agent completed but no PR/push (partial work) | human-required |
| Agent failed, hit errors, looped | human-required |
| Agent blocked, needs input | human-required |
done — only humans do thattodo — triggers auto-dispatch, creates duplicate agentsin-review when uncertainhuman-required if agent output shows errors, loops, or incomplete worksybra-cli --json update <id> --status <new-status>
Actions:
sybra-cli --json update task-abc --pr 42
sybra-cli --json update task-abc --status in-review
Actions:
sybra-cli --json update task-abc --status human-required
Actions: status=human-required (partial work, no push detected).