القائمة
Research the codebase before implementing a task. Use Grep/Glob, semantic search, or a read-only explore subagent to find relevant files, patterns, existing code, and test files.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | ralph-research |
| description | Research the codebase before implementing a task. Use Grep/Glob, semantic search, or a read-only explore subagent to find relevant files, patterns, existing code, and test files. |
Use the user's topic (or the current task text) as the research focus.
Search the codebase for:
Return a structured summary:
path/to/file:line — relevance descriptionFunctionName in path/to/file:line — what it doespath/to/test_file — what it testspackage/module — how it's used and what might breakRalph's per-loop execution contract — one task from fix_plan.md, the RALPH_STATUS exit block, epic-boundary QA deferral, and the dual-condition EXIT_SIGNAL gate. Invoke at the start of every Ralph loop so the response follows the contract the harness depends on.
Eval-first principles and cost-aware model routing for the Ralph loop. This skill should be used before committing budget to a MEDIUM+ task or when choosing a sub-agent: articulate the behavior to verify first, then route by task type (docs/tools → Haiku, code → Sonnet, arch → Opus, with an Opus escalation after repeated QA failures). Integrates with lib/complexity.sh and the optional sdk/ralph_sdk/cost.py::select_model.
Token-hygiene pass for the Ralph loop. This skill should be used before reading another large file or near the end of a Continue-As-New window: it drops stale file reads, prefers targeted Grep over full-file Read, and consolidates repeated file-scan patterns to stop the drift where each iteration re-reads the same file and burns prompt cache. Works with the SDK ContextManager (sdk/ralph_sdk/context.py) and the Continue-As-New trigger.
Run, monitor, and continuously improve Ralph (autonomous dev loop for Claude Code) against a Linear backlog. This skill should be used when the user says "run ralph", "start ralph", "ralph campaign", "monitor ralph", "restart ralph", "ralph against TAP-### / ENG-### / <ISSUE-ID>", or wants Ralph to chew through filed epics autonomously with the orchestrator filing follow-up Linear issues for the friction patterns it observes. Encodes proven startup, monitor-filter, kill-safety, and subagent-delegation patterns. Keeps the orchestrator's context window tiny by delegating Linear writes, commit verification, and bulk log analysis to subagents.
Research-before-coding workflow for the Ralph loop. This skill should be used before writing a new utility, helper, or abstraction: it searches the repo, installed libraries, and public registries for an existing solution first, delegating deep search to the ralph-explorer sub-agent (Haiku). Use it whenever the next task — a fix_plan item or a Linear issue — says "add/implement/build/wrap/integrate" something that sounds generic.
Pre-commit / epic-boundary quality pass for the Ralph loop. This skill should be used at an epic boundary to prune dead code, duplicated logic, unused imports, redundant comments, and speculative error handling introduced during the loop's Green phase. It removes, never adds — the diff should end smaller than it started.