ralphx-swe

RalphX SWE Skill — Autonomous Pipeline Playbook

Skill vs Guide: Call v1_get_agent_guide for tool schemas and sequencing rules. This skill teaches judgment: when to act vs observe, how to handle edge cases, what events mean for decision-making. Zero overlap with the guide's API reference content.

---

1. Bootstrap — Start Here Every Session

Two steps before taking any pipeline action:

Canonical tool naming (read this before any tool call):

Examples in this skill use canonical RalphX method names: v1_*

Host mappings:
- RalphX external MCP methods: v1_*
- Claude/Codex MCP wrappers in some environments: mcp__ralphx__v1_*
- ReefBot integration: ralphx__v1_*

Never invent a namespace from this skill name.
Never call mcp__ralphx-swe__*.

Step 1 — Check attention items (find what needs action right now):

v1_get_attention_items(project_id)
→ Returns escalated_reviews, failed_tasks, merge_conflicts.
→ Address these before doing anything else.

Step 2 — Load tool reference (for argument schemas and preconditions):

v1_get_agent_guide()  → or v1_get_agent_guide(section: "pipeline") for supervision tools

---

2. Core Principles

Observe before act. Most pipeline states are agent-active (executing, reviewing, merging). Your role in those states is to watch, not interrupt. Only take action in waiting states (review_passed, escalated, qa_failed, merge_conflict, merge_incomplete).

Annotate before you intervene. Before calling any action tool, call v1_create_task_note with your reasoning. This creates an audit trail for humans reviewing your decisions.

Always pair UUIDs with titles. Any task ID you surface in a log, message, or annotation must include the human-readable title. Use v1_get_task_detail or v1_batch_task_status to resolve titles. Format: task-{id} ({Title}).

Webhook chat updates should stay human-first. Machine IDs from RalphX webhook events are stored separately in message/session metadata. In normal user-facing chat updates, prefer human titles and project labels; do not dump raw UUID footers unless the user explicitly asks for them.