'codebase' 검색 결과

Review medium to large code changes using checks selected for the actual patch. Analyze the change and surrounding code, assign focused reviews by function, file, or feature, and combine findings with locations, confidence levels, and supporting evidence.

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

• Reviewing patches of roughly 50 to 1,000 lines
• Checking risks specific to a changed feature
• Reviewing changes alongside callers and related implementations

Review the current codebase for ignored errors, embedded credentials, unused exports, and obvious type-safety gaps. Receive a report ordered by severity, with file and line references, while all source files remain unchanged.

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

• Run a quick code quality review
• Check for embedded keys or passwords
• Find missing error handling and unsafe type usage

Run an AI vulnerability scan on uncommitted changes, changes against main, or an entire codebase. Filter candidate files, investigate potential security issues, and review findings with severity ratings, with options to revalidate and export results.

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

• Checking uncommitted changes for vulnerabilities
• Reviewing security issues in changes against main
• Scanning an existing codebase

Find other occurrences of a known bug across a codebase by tracing its root cause. Gradually broaden search patterns, assess matching candidates, assign severity, and document findings with rules to help prevent recurrence.

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

• Finding similar issues after discovering a vulnerability
• Building CodeQL or Semgrep queries from a known bug
• Checking whether similar code shares the same root cause

Scans code for security vulnerabilities with CodeQL by tracing data across functions. Builds and checks analysis databases, models project-specific APIs, and saves findings in SARIF, a structured results format, with broad or focused scan options.

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

• Scanning a codebase for security vulnerabilities
• Tracing untrusted input through custom APIs
• Choosing broad or high-precision security scans

Audits arithmetic code for mixed units, decimal precision mistakes, and scaling errors. Adds comments identifying each value’s units and produces a summary of findings, unit definitions, and files reviewed.

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

• Reviewing token amounts and price conversions in DeFi code
• Checking WAD/RAY scaling errors
• Documenting units and precision in existing formulas

Build or update a Figma design system to match a codebase. Organize reusable design values, light and dark themes, component variants, and documentation, then check component structure, appearance, and bindings to those values.

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

• Build a Figma component library from existing code
• Set up shared design values and light and dark themes
• Create components with variants and variable bindings

Investigate unfamiliar codebases before fixing bugs, adding features, or refactoring. Follow relevant code paths, plan focused changes, and verify results, while recording useful discoveries in .notebook/ so later sessions can build on earlier investigation.

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

• Investigate and fix bugs in unfamiliar code
• Add features following existing project conventions
• Trace and document authentication or other flows

Analyze TypeScript and JavaScript code for reusable design structures known as GoF patterns. Get detection reports, quality scores, and prioritized refactoring suggestions that account for the frameworks and libraries already used in the project.

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

• Find existing design patterns in a codebase
• Plan refactoring for complex conditionals
• Evaluate the quality of a pattern implementation

Learn the complete OpenSpec workflow through a small task in an actual codebase. The agent explains each stage while creating a proposal, specifications, design, and tasks, then implements the change and archives its records.

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

• Learning OpenSpec through a real code change
• Understanding proposals, specifications, designs, and tasks
• Practicing a complete change cycle with a small fix

Introduce nullable reference types into an existing C# project, making explicit which references may be null. Plan a staged migration, resolve compiler warnings, and clarify public API annotations while preserving runtime behavior.

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

• Adopting nullable reference types in an existing C# project
• Migrating a large codebase file by file
• Clarifying nullability in public APIs

Examine a plan or design through focused questions, each with a recommended answer. Work through connected decisions to reach shared understanding, using codebase exploration to resolve questions that the code can answer.

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

• Stress-testing a plan before moving forward
• Clarifying unresolved design decisions
• Working through dependencies between decisions

Organize large coding tasks with Claude Fable directing lower-cost subagents. Delegate bounded research, edits, and tests, then have Fable verify evidence, resolve conflicting findings, integrate changes, and review the final result.

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

• Split a large codebase investigation across subagents
• Delegate independent, narrowly scoped code edits
• Distribute targeted tests and log summaries

Build a compact overview of an unfamiliar codebase with TLDR. Summarize its file tree, functions, classes, and calls between components, then highlight complex functions while reducing the amount of source text the agent needs to read.

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

• Getting oriented in an unfamiliar codebase
• Reviewing key functions and classes
• Understanding calls between project components

Investigate how an existing codebase works and document its components, connections, and file references. Combine current code findings with historical notes to produce a research document grounded in specific paths and line numbers.

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

• Understanding an existing authentication flow
• Documenting connections between system components
• Reviewing past decisions alongside current code

Get oriented in an existing codebase by identifying its technologies, important files, and architecture. The skill gathers your goals and creates a YAML handoff record with priorities and suggested next actions.

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

• Getting started in an existing project
• Understanding technologies and important files
• Recording goals and initial priorities

Search a codebase with WarpGrep to find functions, variables, imports, and other text. Use regular expressions to match text patterns, limit searches to a directory, or replace the contents of a specified file.

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

• Finding authentication code
• Locating functions with regular expressions
• Checking imports in a source directory

Turn feature requests and conversation context into an implementation plan and handoff document. Review existing code, clarify complex requirements, and organize concrete tasks, affected files, verification steps, assumptions, and risks for review before implementation.

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

• Planning a feature for an existing codebase
• Clarifying requirements for a complex feature
• Defining tasks and checks for a new project

Turn a broad coding request into a concrete work plan grounded in the codebase. After user approval, it documents affected files, decisions, dependencies, and verification steps so a separate worker can carry out the implementation.

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

• Planning a large feature before coding
• Turning a vague request into defined tasks
• Preparing an implementation handoff

Audit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to improve or refactor architecture.

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

Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says 'it works but it is slow and getting worse'. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.

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

Generate a complete, beginner-friendly explanation of an entire code repository as a set of markdown files. Maps the repo structure with `treecap` (installing it if missing), studies the actual source, then writes a `CODE_EXPLANATION/` folder containing an `OVERVIEW.md` plus numbered deep-dive files (01_architecture.md, 02_models.md, ...) that explain how the code is built, what it does, and how the pieces fit together — illustrated with real code excerpts. Use this skill whenever the user wants to understand, document, onboard onto, or get a walkthrough of a codebase: phrases like "explain this repo", "explain the code", "code explanation", "walk me through this codebase", "help me understand how this is built", "document the architecture", or "what does this project do" — even if they don't say the word "skill". Prefer this over ad-hoc summaries whenever the goal is a durable, written explanation of a whole repo.

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

Land a change everywhere the same fact is stated — enumerating the full surface inventory (landing copy, docs, machine-readable summaries, changelog badges repeated across every page, sitemap, README, descriptions embedded in code, and untyped frontend consumers of typed responses), generating a surface instead of restating it, drift tests where you cannot generate, never hand-maintaining a copy of a surface another codebase owns, shipping a paired PR when you change a format a different codebase decodes, and keeping overloaded product words apart. Use when adding or renaming a user-facing feature, editing product/marketing copy or docs, renaming a serialized response field, changing a serialization or share-link format, wiring one repo's output into another's checks, or reviewing a PR that touched only one place a fact appears.

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

When given a project codebase, this skill observes the important functions in the codebase for future action.

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