'maintainability' 검색 결과

Review Archify issues, pull requests, and code by weighing user value, implementation and maintenance costs, and wider impact. Use evidence to decide whether work is worthwhile, compare alternatives, and identify questions that still affect the decision.

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

• Prioritizing reported issues
• Reviewing the cost and impact of a pull request
• Assessing code maintainability

Review source code for readability, complexity, duplication, and maintainability without changing files. Receive a structured report with prioritized issues, refactoring suggestions, positive findings, and estimates of technical debt—the work needed to address accumulated code problems.

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

• Review the quality of an authentication module
• Find duplicate code and overly long methods
• Assess accumulated code problems and repair effort

Review system architecture and major design changes for scalability, resilience, and maintainability. Identify risks, compare design tradeoffs, and document recommendations and next steps across services, APIs, data storage, security, and deployment.

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

• Reviewing microservice boundaries
• Assessing a move to event-driven architecture
• Comparing serverless and container deployment

Review code for security, performance, quality, and maintainability. Get findings organized by severity, with file locations, explanations of impact, and example fixes, plus code metrics and complexity comparisons for refactoring reviews.

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

• Reviewing a pull request before merging
• Checking code for security risks
• Finding performance improvement opportunities

Improve existing code structure while preserving its behavior. Review dependencies and tests, identify maintainability problems such as duplication or long functions, and plan small changes with testing, reversible commits, and a final comparison of results.

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

• Splitting long functions into smaller, clearer functions
• Removing duplicated logic and unused code
• Planning improvements to hard-to-maintain legacy code

Improve existing code structure while preserving its behavior, using Martin Fowler's refactoring approach. Assess tests, identify structural problems, agree on a phased plan, and make small, tested changes with reversible commits and before-and-after comparisons.

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

• Splitting long functions into clearer responsibilities
• Removing duplicate or unused code
• Planning gradual improvements to legacy code

Refactor JavaScript using ES6+ features to make code easier to read and maintain. Covers asynchronous operations with async/await, modules, and functional patterns that transform data without changing the original values.

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

• Refactoring legacy JavaScript
• Migrating callbacks to async/await
• Building data transformation pipelines

Review DAX formulas, the expressions used for calculations in Power BI, and propose clearer, more maintainable alternatives. Identify repeated calculations, costly filtering, and error-handling issues, then explain changes and recommend ways to test them.

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

• Reviewing slow calculations in Power BI reports
• Making complex DAX formulas easier to read
• Improving division and blank-value handling

Review a Power BI data model’s tables, relationships, storage choices, performance, maintainability, and security. Use the findings to identify design issues and build a prioritized improvement plan with concrete recommendations and implementation guidance.

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

• Reviewing a Power BI model before production release
• Investigating slow queries and oversized models
• Checking table relationships and storage choices

Review C#/.NET code for design patterns, separation of responsibilities, and common implementation issues. Receive actionable recommendations covering maintainability, testing, performance, and security without changing the code.

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

• Review design patterns in C#/.NET code
• Check separation of responsibilities before refactoring
• Identify dependencies that make testing difficult

Run Gemini CLI to review code, assess technical plans, and analyze large collections of files. Choose a model and execution settings for the task, then capture findings about security, maintainability, architecture, or technical debt.

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

• Reviewing security and quality across multiple files
• Checking architecture plans for missing components
• Analyzing the structure of a large codebase

Review code changes for security, performance, correctness, and maintainability. Get findings tied to files and lines, severity ratings, practical suggestions with code examples, and a recommendation to approve, request changes, or discuss further.

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

• Reviewing a pull request before merging
• Checking authentication and injection risks
• Finding excessive database queries and resource leaks

Review recent code changes for duplication, maintainability, and wasted work, then apply straightforward improvements. The workflow combines three parallel reviews, prioritizes small, low-risk fixes, and checks the edited code with relevant tests or project checks.

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

• Cleaning up code after implementation
• Polishing changes before opening a pull request
• Reducing duplication in recent changes

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

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

• Reviewing a pull request before merging
• Getting a second opinion on AI-written code
• Checking authentication or data access code

Review code changes and files for bugs, security risks, performance problems, design issues, and test coverage. Receive a structured report with prioritized findings, concrete improvement examples, positive feedback, and an overall review verdict.

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

• Reviewing a pull request
• Auditing code quality and security
• Finding refactoring opportunities

Review code changes for security, performance, correctness, and maintainability. Get findings tied to files and lines, severity ratings, practical suggestions with code examples, and a recommendation to approve, request changes, or discuss further.

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

• Reviewing a pull request before merging
• Checking authentication and injection risks
• Finding excessive database queries and resource leaks

Writes and reviews Lean 4 proofs, machine-checked arguments for mathematics or specifications. Follows Mathlib conventions to organize definitions and lemmas, fill proof gaps, refactor lengthy proofs, and establish automated checks for unproved claims and style.

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

• Formalizing mathematics or specifications in Lean 4
• Filling sorry placeholders in proofs
• Splitting long proofs into reusable lemmas

Get independent code reviews of uncommitted changes, branch differences, or individual commits using Codex or Antigravity. Receive findings with severity, locations, impact, and suggested corrections, and compare where the two reviewers agree or differ.

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

• Reviewing uncommitted changes for bugs
• Comparing Codex and Antigravity on the same branch diff
• Reviewing a specific commit for security issues

Improve CircleCI build and test pipelines by identifying slow or unreliable jobs, then adjusting caching, data sharing between jobs, triggers, and parallel execution. Receive incremental configuration changes with expected effects, validation criteria, and rollback guidance.

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

• Reduce long CI build and test times
• Improve dependency cache reuse
• Remove duplicate jobs and unnecessary runs

Audit Claude, Codex, or Pi configuration, instruction conflicts, hooks, and MCP connections to external tools. It also checks safeguards for maintaining AI-assisted projects and returns prioritized findings with evidence and concrete corrective or diagnostic steps.

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

• Investigate agent settings or instructions that seem ineffective
• Audit hooks, MCP connections, and permission boundaries
• Check verification gaps and stale project guidance

Review code for readability, security weaknesses, performance bottlenecks, test quality, and ease of maintenance. Receive findings grouped by importance, with explanations and concrete suggestions that reflect the project's context and constraints.

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

• Reviewing code quality before merging changes
• Checking security and sensitive data handling
• Finding slow queries and unnecessary API calls

Guide code changes in iPolloWork by reusing existing implementations, limiting new files and dependencies, and keeping responsibilities clear. Review runtime costs, run focused checks, and audit the final changes for duplication and maintainability issues.

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

• Checking for reusable code before implementing a feature
• Removing duplicate implementations during refactoring
• Reviewing the need for new files and dependencies

Review SwiftUI projects for outdated APIs, data flow, layout, accessibility, and performance issues. Get findings organized by file, with brief before-and-after code examples and a prioritized summary of the changes that matter most.

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

• Reviewing an existing SwiftUI app
• Checking for deprecated APIs
• Checking accessibility and adaptive layouts

DO NOT INVOKE when the primary request explicitly asks to convert, migrate, modernize, or rewrite a legacy/old-style project to SDK style; use msbuild-modernization. Migration prompts often mention ToolsVersion, explicit Compile/Reference entries, packages.config, or Microsoft.CSharp.targets, but merely reviewing or auditing a file that contains those patterns remains in scope here. USE FOR broad review, audit, lint, or maintainability/correctness checks of project/build files, including custom targets; prioritized cross-cutting findings; discrete anti-patterns; F# ordering/FS0039; cross-platform paths; and focused Import safety verdicts. Review/audit is analysis-only unless fixes are requested. For concrete property/item defects use property-patterns/item-management; use target-authoring for implementation and extension-points for NuGet auto-import/layout discovery. Exclude non-MSBuild systems.

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