'evidence-based' 검색 결과

Evaluate company leaders by comparing public promises with results and reviewing how they spend company funds. Examine acquisitions, share buybacks, governance, employee and customer feedback, and succession plans to produce an evidence-based management assessment.

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

• Checking whether a CEO delivered on public promises
• Reviewing acquisitions, share buybacks, and dividends
• Examining executive pay, ownership, and related-party transactions

Verify whether a reported vulnerability is fixed in the current code without changing repository files. Trace the original attack path, examine possible bypasses and legitimate behavior, and return an evidence-based verdict for each supplied finding.

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

• Verify remediation of a reported vulnerability
• Check for bypasses around a security fix
• Verify a fix after code moves or refactoring

Assess a fixed patch or pull request diff before merging. Trace affected behavior, evaluate regression risks, tests, and recovery options, then provide an evidence-based recommendation and advisory automatic-merge eligibility without modifying or merging the patch.

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

• Assess a generated patch before merging
• Trace how a pull request affects production behavior
• Evaluate tests and rollback options

Split debugging, audits, searches, and code questions into read-only tasks for sub-agents. Combine their structured reports into an evidence-based answer, requesting follow-up investigations when findings conflict or leave important gaps.

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

• Investigating a bug without changing code
• Understanding repository structure and design
• Comparing architectures from multiple perspectives

Audit paid-ad landing pages for message consistency, mobile usability, accessibility, performance, forms, consent, tracking, and destination safety. Get evidence-based findings and recommendations ready for experiments to address obstacles to completing the intended action.

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

• Checking consistency between ads and landing pages
• Reviewing mobile layouts and accessibility
• Finding form friction and error-state issues

Review X Ads tracking, campaign goals, keyword and conversation targeting, creative, budgets, and brand safety. Receive an evidence-based diagnosis and prioritized recommendations, with gaps in account information and unavailable features clearly marked.

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

• Checking X Pixel and conversion tracking
• Reviewing keyword and conversation targeting
• Prioritizing creative, budget, and brand safety improvements

Audit how advertising platforms, GA4, and app measurement tools assign credit for conversions. Compare event definitions, reporting windows, and duplicate handling to explain discrepancies and produce an evidence-based measurement improvement plan.

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

• Investigating discrepancies between Meta and Google conversions
• Checking GA4 against advertising platform reports
• Reviewing app conversion measurement

Review OpenClaw frontend code and rendered screens for departures from Carapace design rules, accessibility issues, responsive defects, and inconsistent copy. Produce evidence-based JSON and Markdown reports that distinguish documented violations from judgment-based suggestions and guide narrowly scoped fixes.

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

• Check compliance with Carapace design rules
• Review desktop and mobile interfaces
• Audit accessibility and brand copy

Audit Google Drive sharing without changing permissions. Use gog to identify public links, external sharing, broad domain access, potentially outdated grants, and ownership anomalies, then document affected files and supporting evidence.

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

• Review public links and external sharing
• List files accessible to a specific person
• Check broad domain access and potentially outdated grants

Evaluate a feature idea before turning it into requirements using six sequential questions. Examine customer demand, current workarounds, a specific user's pain, and the smallest useful solution, then save an evidence-based assessment with a verdict and next steps.

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

• Validating customer demand before writing requirements
• Narrowing a feature to its smallest useful version
• Separating customer evidence from assumptions

Analyze short web fiction to understand its central premise, emotional progression, twists, characters, and writing techniques. Produce an evidence-based report and supporting files that can inform a new story without copying distinctive elements.

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

• Studying the structure of short web fiction
• Tracing emotional buildup and plot twists
• Examining character roles and opening or ending techniques

Review token contracts and the protocols that accept them for ERC20/ERC721 compliance, privileged controls, and unusual transfer behavior. Produces evidence-based risk assessments and prioritized fixes, with supply and holder analysis when deployed contract details are provided.

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

• Checking ERC20/ERC721 implementations against their standards
• Reviewing support for tokens with unusual transfer behavior
• Assessing administrator powers and upgrade risks

Compare implementation code with a specification, whitepaper, or design document. It checks individual requirements, independently challenges reported mismatches, and writes evidence-based reports covering missing or partial implementation, contradictions, undocumented behavior, and requirements that cannot be judged.

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

• Check an implementation against a specification
• Compare protocol code with a whitepaper
• Verify guarantees stated in a README

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

Plan the first 90 days as a VP or CPO product leader through organizational interviews, validation, and evidence-based action. Build a people assessment, identify unwritten priorities, and choose three to five changes grounded in what you learn.

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

• Planning the first 90 days in a product leadership role
• Preparing questions for the CEO before accepting a CPO offer
• Validating organizational findings before making changes

Verify whether a reported vulnerability is fixed in the current code without changing repository files. Trace the original attack path, examine possible bypasses and legitimate behavior, and return an evidence-based verdict for each supplied finding.

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

• Verify remediation of a reported vulnerability
• Check for bypasses around a security fix
• Verify a fix after code moves or refactoring

Assess a fixed code patch for behavior changes, regression risks, test coverage, and recovery options. Receive an evidence-based report and structured assessment indicating whether it is ready to merge and qualifies as an automatic merge candidate.

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

• Reviewing the risks of an AI-generated patch
• Checking affected behavior before merging a pull request
• Assessing whether tests protect changed behavior

Review a pull request using repository checks, verified code references, and current official documentation. Assess correctness, security, structure, and unnecessary code, then post one consolidated GitHub review with inline findings and an evidence-based verdict.

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

• Review a pull request before merging
• Check code structure and unnecessary comments
• Verify dependency changes against official documentation

Create an evidence-based plan for modernizing an existing system. Analyze code and dependencies, research technology choices, and produce domain-specific migration plans with testing, rollback steps, and a consolidated roadmap for developers to execute.

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

• Planning a gradual replacement of a legacy system
• Comparing service separation and consolidation strategies
• Preparing a language or framework migration

Assess AI products, agents, MCP servers, and skill packages through authorized security testing. It models access boundaries, tests injection and tool misuse, and produces evidence-based reports with business impact, defensive successes, and concrete remediation steps.

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

• Assessing an AI agent before release
• Testing prompt injection and tool misuse
• Auditing skill packages, plugins, and MCP servers

Diagnose command failures before attributing them to sandbox restrictions, which limit access to files and networks. Check execution methods, command matching, and network behavior, then prepare an evidence-based report for the person responsible for settings.

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

• Investigating permission errors such as EPERM
• Separating network restrictions from hostname failures
• Checking why an excluded command still fails

Investigate bugs by tracing symptoms through code and recent changes, reproducing failures, and testing a specific cause before fixing it. Produce a focused correction, a regression test to catch recurrence, and an evidence-based debugging report.

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

• Investigate errors that keep returning after fixes
• Trace a regression through recent changes
• Analyze failures that occur only in certain environments

Follow a structured Claude Code curriculum with tracks for different goals. Record concrete evidence from project exercises, unlock modules when prerequisites are complete, and check scheduled reviews while keeping progress data inside the current project.

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

• Learn a first daily workflow with Claude Code
• Practice reusable workflows in a real project
• Keep evidence of completed learning exercises

Create a GitHub pull request from the current branch with a structured title, a clear explanation of behavior changes, and recorded check results. For UI changes, attach before-and-after screenshots so reviewers can assess the visual differences.

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

• Preparing and publishing a PR from the current branch
• Writing a PR description backed by verification results
• Attaching before-and-after screenshots for UI changes