'correctness' 검색 결과

Build, debug, and refactor JavaScript applications for browsers and Node.js. Covers asynchronous tasks with async/await, module organization, performance checks, and test creation, with explicit error handling and modern ES2023+ syntax.

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

• Build a vanilla JavaScript application
• Fix errors in asynchronous API requests
• Organize code into ESM modules

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

Fix a validated or plausible security vulnerability with a focused code change, then verify that the attack no longer works and legitimate behavior remains intact. Report when existing code is safe or essential evidence is missing.

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

• Fix a reported vulnerability and verify the result
• Check for alternate inputs that bypass a proposed fix
• Confirm that a security patch preserves legitimate behavior

Review selected files for bugs by reading full source code, callers, and related implementations. Apply detailed checklists and investigate suspected issues, then report evidence, confidence levels, and suggested fixes.

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

• Review selected files in a critical code change
• Investigate concerns raised by an initial review
• Check complex state transitions and object lifecycles

Audit one datafusion-spark function against Apache Spark 4.2.0. Compare source code, accepted types, and edge cases, verify expected results with PySpark, then fix differences and record remaining gaps as issues and disabled tests.

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

• Auditing a function for Spark compatibility
• Checking NULL, overflow, and ANSI mode behavior
• Finding missing SQL test coverage

Fix a validated or plausible security vulnerability with a focused code change, then verify that the attack no longer works and legitimate behavior remains intact. Report when existing code is safe or essential evidence is missing.

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

• Fix a reported vulnerability and verify the result
• Check for alternate inputs that bypass a proposed fix
• Confirm that a security patch preserves legitimate behavior

Build or review SwiftUI interfaces using Liquid Glass on iOS 26 and later. Apply native glass effects to controls, group related elements, check interaction and transitions, and provide fallback visuals for earlier iOS versions.

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

• Add Liquid Glass to existing buttons and cards
• Review glass effect usage and modifier order
• Group glass elements and add animated transitions

Review a pull request for code quality, correctness, security, tests, and documentation. Receive structured findings ranked by severity, with file references, approval status, positive highlights, and questions that need clarification.

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

• Reviewing a pull request before merging
• Checking changes against the original plan
• Auditing error handling and validation of AI output

Evaluate staged Git changes before committing using an LLM, a language model acting as a reviewer. Receive correctness, completeness, and safety scores, plus issues by severity, to decide whether to fix, commit, or stop.

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

• Evaluate significant changes before committing
• Review changes in unfamiliar code
• Check changes to security-sensitive code

Audit Claude Code and Codex hooks, actions triggered by agent events. Check commands, trigger conditions, blocking behavior, and timeouts to identify why hooks fail to run, fail to block actions, or delay the agent.

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

• Validate hook settings before committing
• Investigate hooks that never run
• Check policy hooks that fail to block actions

Review code changes and pull requests for correctness, security, performance, and test quality. The skill helps prioritize issues, write specific and constructive feedback, and create shared review checklists and standards for a development team.

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

• Reviewing code changes and pull requests
• Writing review comments with clear priorities and fixes
• Creating shared review checklists for a team

Review custom dotnet new templates before publishing. Check required fields, parameter types and defaults, command name conflicts, and constraints, then receive findings grouped by severity with concrete fixes for errors and warnings.

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

• Checking template.json before publishing
• Investigating templates missing after installation
• Reviewing parameter types and default values

Optimize .NET loops with SIMD, which processes multiple values in one operation, or review existing SIMD code. Check behavioral equivalence, memory safety, platform fallbacks, and benchmarks to establish whether the optimization is correct and worthwhile.

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

• Optimize numeric loops with SIMD
• Review existing vectorized code for correctness
• Test boundary lengths and overlapping buffers

Prepare scientific figures for papers, reports, and saved deliverables by checking data fidelity, chart choice, labels, axes, and color consistency. Verify exported figures for overlapping text and readability while keeping fonts, palettes, and framing configurable.

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

• Preparing scientific figures for a paper or report
• Checking excluded data and summary statistics
• Improving labels, axes, and color consistency

Delegate a focused coding, research, review, or verification task to a separate DevSpace agent. Choose an available worker, provide a self-contained brief, inspect or wait for results, and continue related work with the same agent.

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

• Requesting an independent correctness or security review
• Investigating a bounded part of a codebase
• Delegating an isolated change with clear acceptance criteria

Review changes to a multilingual source code parser, focusing on whether relationships between code elements are correct. Check consistency across languages and verify that test examples reproduce the issue and actually validate the fix.

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

• Checking constructor call and instantiation relationships
• Reviewing name resolution and scope handling
• Checking whether a parser fix applies to other languages

Review concrete code changes for defects, compatibility problems, repository-rule violations, and unnecessary code. Produce evidence-based findings and, when explicitly requested, make minimal cleanup changes while checking that existing behavior is preserved.

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

• Reviewing a pull request or commit range
• Inspecting staged and unstaged changes
• Finding debug residue and duplicate code

Review resolved dependency versions and relevant code for security vulnerabilities. Get findings with evidence, impact, and targeted remedies, distinguishing published dependency warnings from exploit paths demonstrated in the project.

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

• Check dependencies for known vulnerabilities
• Trace untrusted input to sensitive operations
• Locate potential secrets in committed files

Run the R code review protocol on R scripts. Checks code quality, reproducibility, domain correctness, and professional standards. Produces a report without editing files. Make sure to use this skill whenever the user wants their existing R code evaluated or audited — not when they want new analysis written. Triggers include: "review my R script", "check my R code", "is my code replication-ready", "audit this R file", "does this code follow conventions", "will this reproduce", "check my analysis script", "code review", "review-r", or when the user has an existing .R file and wants quality feedback rather than new code.

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

Reviews whether a design is SOUND — solving the right problem, derived from its stated goals and constraints — and emits ranked, evidence-backed findings, not edits. Read when asked to 'review this design', 'is this design sound', 'pressure-test this proposal', 'do a design review', 'does this solve the right problem', 'poke holes in this spec', 'should we build this', or to critique a proposal / spec / ADR / architecture or product decision. Do NOT read when the user wants to AUTHOR one of these — routing a new proposal is frame-a-proposal, a spec is write-a-spec, a decision record is record-a-decision, a postmortem is write-a-postmortem. Do NOT read for code review of a diff, or to fact-check individual claims (that is a correctness pass, a different job).

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

Review of a PR, branch, or your own uncommitted work across eight dimensions — security, correctness, test coverage, API/compatibility, usability, documentation, code quality, performance. Sizes the diff, reviews inline or fans out reviewers off a shared brief, verifies findings against code, reports a grouped list with a shape verdict, fixes on approval. Use for "review this PR", "/pr-review 3011", or a pre-flight self-review before submitting; add "thorough" for adversarial verification.

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

Guide a Chinese-speaking user through code or a PR while reviewing correctness. Trigger on 帮我review, 带我读代码, or an explicit implementation walkthrough.

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

Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.

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

Add or change a named Pallas/Mosaic kernel, including its reference implementation, correctness tests, wrapper, or requested tuning.

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