القائمة
This skill should be used only when the user explicitly asks to use `$ralphharness-feedback`, or explicitly asks RalphHarness in Codex to draft or submit feedback.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Canonical rules for the external-reviewer bootstrap, liveness heartbeat freshness gate, and convergence detection. This skill is the single source of truth for reviewer-warmup behavior.
Use only when the user explicitly invokes `$ralphharness`, requests RalphHarness in Codex, asks RalphHarness to handle a named phase, or explicitly requests autonomous or quick mode or continuation without pauses.
Load this skill suite for any spec that involves end-to-end testing, browser automation, Playwright, MCP browser tools, VE tasks, user flow verification, UI testing, or integration tests that drive a real browser. Covers session lifecycle, environment setup, navigation anti-patterns, stable-state detection, auth flows, selector stability, and cleanup guarantees.
This skill should be used only when the user explicitly asks to use `$ralphharness-design`, or explicitly asks RalphHarness in Codex to run the design phase.
This skill should be used only when the user explicitly asks to use `$ralphharness-design`, or explicitly asks RalphHarness in Codex to run the design phase.
This skill should be used only when the user explicitly asks to use `$ralphharness-implement`, or explicitly asks RalphHarness in Codex to run implementation for approved tasks, quick mode, or an explicit continue request.
| name | ralphharness-feedback |
| description | This skill should be used only when the user explicitly asks to use `$ralphharness-feedback`, or explicitly asks RalphHarness in Codex to draft or submit feedback. |
| metadata | {"surface":"helper","action":"feedback"} |
Use this to capture product feedback or bug reports for RalphHarness.
gh is available and the user wants submission, create a GitHub issue.gh is unavailable or the user only wants a draft, produce a ready-to-paste issue body and the repository issue URL.Keep the report concrete. Include expected behavior, actual behavior, reproduction steps, and any relevant state files or logs.