'codebase' 검색 결과

코드를 읽고 구조, 주요 모듈과 시작 절차를 위키로 정리합니다. Mermaid 구성도와 흐름도를 만들고 소스 링크가 있는 참고 자료를 남깁니다.

• 낯선 코드의 전체 구조 파악하기
• 구성도와 처리 흐름도 만들기
• 새 팀원을 위한 참고 자료 작성하기

코드의 함수와 호출 관계, 실행 흐름을 연결된 도표로 만들어 브라우저에서 탐색할 수 있게 합니다. Cloudflare를 통한 원격 공유도 지원합니다.

• 처음 접하는 코드의 전체 구조 파악
• 함수 호출과 실행 흐름 확인
• 조작 가능한 코드 도표의 원격 공유

코드 행 수, 사용 언어, 파일 수, 주석 비율을 집계하여 개발 프로젝트의 규모와 구성을 파악합니다. 언어별 필터링과 파일별 확인도 지원합니다.

• 프로젝트의 코드 규모를 파악합니다
• 사용 언어와 파일 수를 확인합니다
• 코드와 주석의 비율을 확인합니다

Builds or updates a Figma design system library from an existing codebase. Helps keep reusable design components aligned with the components already shipped in a product, giving design teams a reference that reflects the implementation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a Figma library from an existing codebase
• Updating a design library to match shipped components
• Aligning design references with implementation

Launch the Understand Anything web dashboard to explore an existing codebase knowledge graph, a map of its structure and relationships. Open the current project or a specified directory and receive the local access URL.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explore an analyzed codebase visually
• Open the current project's dashboard
• View graph data from another project directory

Audit a codebase for unnecessary complexity, including dead code, duplicated state, redundant interfaces, and obsolete compatibility paths. Receive evidence-backed simplification candidates, or authorize changes that remove justified targets and validate the behavior that must remain.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding code that can be safely removed
• Consolidating duplicated state or APIs
• Reviewing obsolete compatibility paths and design records

Analyze a codebase and create a CLAUDE.md guide for future Claude Code sessions. Capture build and test commands, explain the overall architecture, and incorporate relevant information from existing documentation and development rules.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a CLAUDE.md guide for a codebase
• Document build, lint, and test commands
• Explain the overall code architecture

Analyze a codebase to create project-specific AGENTS.md instructions and supporting rule files. Detect the package manager and relevant conventions, preview proposed changes, or update existing guidance when the project’s tools change.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create agent instructions tailored to an existing project
• Generate a minimal AGENTS.md file
• Refresh instructions after changing development tools

Create and maintain project documents in conductor/ covering the product, technology stack, development workflow, and work units. Extract context from existing code, check document consistency before implementation, and update documentation as the project evolves.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up context documents for a new project
• Document an existing codebase for onboarding
• Check project documents before implementation

Analyze a codebase to document its technologies, architecture, dependencies, and implementation patterns. Produce a Markdown reference with optional diagrams, code examples, and guidance for adding features consistently with the existing design.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understand an unfamiliar codebase's architecture
• Document components, dependencies, and data flow
• Create guidance for adding features consistently

Documents a codebase with linked AGENTS.md files that explain each directory, important files, dependencies, and working rules. It can also update existing documentation while preserving human-written notes and checking that the document hierarchy remains consistent.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting an unfamiliar codebase for AI agents
• Recording directory-specific rules and dependencies
• Updating documentation after structural changes

Route codebase exploration, file analysis, and web research through context-mode tools in Antigravity CLI. Process large outputs outside the conversation and return focused findings, with indexed content available for later searches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explore a codebase and summarize key findings
• Extract and count information in a file
• Index web content for follow-up searches

Scan a codebase for technical debt—issues that make future maintenance harder—and prioritize fixes using business impact and effort. Generate a ranked backlog, sprint allocations, and trend reports to assess cleanup work over time.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess technical debt across a codebase
• Prioritize refactoring for the next sprint
• Compare debt levels before and after cleanup

Analyze a codebase to identify valuable assets, attack entry points, and realistic abuse paths. Produce a concise Markdown threat model that explains risk priorities, distinguishes existing protections from proposed mitigations, and makes assumptions explicit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Map attack entry points in a codebase
• Assess threats within a specific project directory
• Prioritize risks to sensitive data and credentials

Analyze a codebase to identify valuable assets, attack entry points, and realistic abuse paths. Produce a concise Markdown threat model that explains risk priorities, distinguishes existing protections from proposed mitigations, and makes assumptions explicit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Map attack entry points in a codebase
• Assess threats within a specific project directory
• Prioritize risks to sensitive data and credentials

Prepare an existing codebase for GSD planning by mapping its structure, ingesting documentation, and initializing project records. The workflow creates or confirms planning files and produces an onboarding summary with findings and the next command to run.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing an existing project for GSD
• Organizing code findings and existing documentation
• Setting up requirements and a roadmap before implementation

Turn an idea into a goal package for /goal. Collect decisions through Plannotator, review testable requirements, explore the codebase, and produce an approved execution plan with verification steps and a clear completion condition.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a rough feature idea into testable requirements
• Agreeing on scope and success criteria before implementation
• Creating an execution plan grounded in the codebase

Package a completed codebase or project directory into a ZIP deliverable. The skill adds a dedicated final step to check project files, create the archive, verify its existence, size, and contents, and explicitly report completion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Delivering a completed codebase as a ZIP file
• Packaging a project directory for handoff
• Checking that a ZIP deliverable was actually created

Package a completed codebase or project directory as a ZIP archive in a separate final step. Verify that the archive exists, inspect its contents, and report the file location with a brief contents summary.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Delivering a completed codebase as a ZIP file
• Packaging projects for download
• Archiving deliverables containing multiple files

Get a quick structural overview of a codebase with Trailmark. The skill identifies programming languages, counts entry points where execution begins, and returns dependency information to support orientation before deeper analysis.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Getting oriented in an unfamiliar codebase
• Checking languages and entry point counts before analysis
• Preparing a structural overview for Vivisect or Galvanize

Assesses smart contract and blockchain codebases against Trail of Bits’ nine-category maturity framework. Produces evidence-backed ratings covering areas such as arithmetic, access controls, documentation, and testing, plus a prioritized improvement roadmap with effort estimates.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing the maturity of a smart contract project
• Identifying gaps in tests and documentation
• Reviewing access controls and operational practices together

Create a Markdown threat model grounded in a codebase. Identify valuable assets, boundaries between trusted and untrusted components, realistic attack paths, and mitigations, then prioritize risks using explicit assumptions about likelihood and impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Map attack paths across a codebase
• Assess threats within a specific project directory
• Prioritize risks to data and credentials

Map a codebase into architectural components, logical groups of source files, and compare their sizes using executable statements and file counts. Produce an inventory, identify unusually large or small components, and recommend where to split or consolidate code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a component inventory before splitting a monolith
• Find components with disproportionately large amounts of code
• Review small components for consolidation

Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing the overall health of an inherited project
• Reviewing exposed credentials and security risks
• Identifying dependency and test coverage gaps