원클릭으로
rp-build
Gather relevant source files for a task, resolve their dependencies, and package everything into a structured context prompt.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Gather relevant source files for a task, resolve their dependencies, and package everything into a structured context prompt.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | rp_build |
| description | Gather relevant source files for a task, resolve their dependencies, and package everything into a structured context prompt. |
Produce a token-optimized context package containing all source files, dependencies, and project structure needed to implement a given task. The output is a structured prompt (XML/plain) ready for an AI agent to act on.
A build_prompt() result containing:
explain_architecture / start_session — understand project layoutbatch_codemap — scan module APIs without reading full filesget_imports_graph / blast_radius — trace dependencies and impactestimate_tokens — verify context fits token budget BEFORE packagingbuild_prompt — package files into final prompt (supports output_file for cross-agent handoff)estimate_tokens before calling build_prompt. If user provides max_tokens, treat it as a hard ceiling.build_prompt calls per module rather than one massive prompt.auto_expand_dependencies=True in build_prompt to automatically include imported files.Produce an architectural design and implementation plan based on task requirements, identifying scope, dependencies, impact, and a step-by-step rollout strategy.
Explore the codebase and export a structured context file (e.g., context.xml) for pasting into an external LLM like ChatGPT or Claude Web.
Trace execution paths from an error or bug report to find the root cause, gathering surrounding context (callers, imports, tests) along the way.
Analyze dependencies, callers, and coupling before refactoring, then produce a safe incremental refactoring plan.
Review recent code changes by gathering git diffs, identifying affected callers and tests, and analyzing for security, performance, and breaking changes.
Identify untested functions by comparing source symbols with test symbols, then prepare context for writing missing tests.