exploring-a-codebase

스타5

포크0

업데이트2026년 6월 1일 21:28

Map an unfamiliar codebase and find the right place to change before editing

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

New1Direction

New1Direction/korgex

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

소프트웨어 개발자컴퓨터 및 수학직·SOC 15-1252

SKILL.md

readonly

name	exploring-a-codebase
description	Map an unfamiliar codebase and find the right place to change before editing
version	1
trust	built-in

Don't edit code you haven't located in context. A few minutes mapping prevents editing the wrong file or breaking a caller you didn't know about.

Orient. Read README/AGENTS.md, the project config (pyproject/package.json/ Cargo.toml), and the directory layout. Learn how it's built, tested, and run.
Find the entrypoints. Locate where execution starts and the main modules. Glob for structure, Grep for symbols.
Trace to the target. For a change, find the exact code that owns the behaviour — search by symbol/string, read the function AND its callers. Confirm you've found the real source, not a generated/duplicated copy.
Learn the conventions. Note the existing patterns (naming, error handling, test layout, comment density) so your change reads like the surrounding code.
For broad exploration, delegate. If mapping spans many files, dispatch a subagent (see delegating-to-subagents) to sweep and report, keeping your context focused.
Only then edit — and read a file fully before you Edit it.

이 저장소의 다른 Skills

같은 저장소

react-doctor

New1Direction/korgex

Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags

2026-06-055

security-scan

New1Direction/korgex

Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done

2026-06-035

browser-automation

New1Direction/korgex

Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable

2026-06-025

verifiable-orchestration

New1Direction/korgex

Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed

2026-06-025

building-an-mcp-server

New1Direction/korgex

Author or connect a Model Context Protocol server so an agent gains new tools

2026-06-015

ci-cd-pipelines

New1Direction/korgex

Build automated pipelines that gate merges and ship reliably

2026-06-015

name	exploring-a-codebase
description	Map an unfamiliar codebase and find the right place to change before editing
version	1
trust	built-in

Don't edit code you haven't located in context. A few minutes mapping prevents editing the wrong file or breaking a caller you didn't know about.

Orient. Read README/AGENTS.md, the project config (pyproject/package.json/ Cargo.toml), and the directory layout. Learn how it's built, tested, and run.
Find the entrypoints. Locate where execution starts and the main modules. Glob for structure, Grep for symbols.
Trace to the target. For a change, find the exact code that owns the behaviour — search by symbol/string, read the function AND its callers. Confirm you've found the real source, not a generated/duplicated copy.
Learn the conventions. Note the existing patterns (naming, error handling, test layout, comment density) so your change reads like the surrounding code.
For broad exploration, delegate. If mapping spans many files, dispatch a subagent (see delegating-to-subagents) to sweep and report, keeping your context focused.
Only then edit — and read a file fully before you Edit it.