Results for “code review”

Trustpilot customer reviews scraper for any company listed on trustpilot.com — given a company domain (e.g. shopify.com, apple.com, shopwagandtail.com) plus optional filters (page number, single star rating 1-5, single language ISO code, verified-only flag, has-company-reply flag, date period last30days/last3months/last6months/last12months, free-text keyword search, and reviewer countryCode client-side filter), extracts paginated reviews with 20+ fields per review: reviewId, reviewUrl, reviewTitle, reviewDescription, reviewRatingScore (1-5), reviewDate (ISO publishedDate), reviewDateOfExperience, reviewLabel, isReviewVerified, reviewer (display name), reviewerId, reviewersCountry (ISO Alpha-2), reviewLanguage, reviewCompanyResponse (the company reply text), plus pagination metadata (currentPage, totalPages, totalCount). Optional flags add reviewer profile metadata (reviewerNumberOfReviews, reviewerProfileIsVerified), reply analysis dates (companyReplyPublishedDate, companyReplyUpdatedDate), extended metadata (reviewSource, reviewVerificationSource, reviewLikes), and review photos. Use when user mentions Trustpilot reviews, scrape Trustpilot, get reviews from Trustpilot, Trustpilot review scraper, Trustpilot customer reviews, extract Trustpilot reviews, Trustpilot review data, download Trustpilot reviews, paginate Trustpilot, paginated Trustpilot reviews, filter Trustpilot reviews by star, filter Trustpilot by language, verified reviews Trustpilot, has reply Trustpilot, company response Trustpilot, Trustpilot reply analysis, brand monitoring Trustpilot, sentiment analysis Trustpilot, competitor reviews Trustpilot, bulk reviews from a Trustpilot page, batch download reviews, trustpilot.com reviews scraping, fake review research Trustpilot, Trustpilot dataset, persona research from Trustpilot reviews, Trustpilot keyword search reviews, Trustpilot date range reviews, review export Trustpilot. Also applies to comparing review trends across competitors, training data for LLM sentiment classifiers, monitoring competitor response time, exporting reviews for BI dashboards, lead generation from active reviewers, ML / fake-review detection, and aggregator sites that display third-party reviews.

The English summary is being prepared. Showing the original description.

Move useful memory notes and MCP server settings from Claude Code or Codex into Muse Code. MCP servers connect agents to external tools; the skill checks compatibility and reports settings that need attention.

• Bring saved preferences into Muse Code
• Import useful project memory notes
• Move MCP server settings to Muse Code

Delegate feature development, large code refactors, and pull request reviews to Codex, Claude Code, or OpenCode as background workers. Use isolated project checkouts, monitor progress, and arrange completion or failure notifications.

• Delegating feature development to a background worker
• Running a large code refactor in an isolated checkout
• Requesting a pull request review from a coding agent

Iteratively improve research by having Claude Code review code, results, and drafts while Codex implements fixes. Repeat until the assessment meets the stopping criteria or the round limit is reached, preserving feedback and unresolved issues.

• Repeating research reviews and fixes before submission
• Checking whether claims match code and experiment results
• Tracking how reviewer concerns are addressed across rounds

Review changes of 1,000 lines or more by dividing work across files, focused areas, and commits. Combine several review methods, check consistency across subsystems, verify bug fixes, and report validated findings alongside a checklist showing review coverage.

• Reviewing feature branches with 1,000 or more changed lines
• Checking a large change before merging
• Finding inconsistencies across commits and subsystems

Turn a Markdown code review into a single HTML file with code changes beside severity-labeled comments. Readers can jump to findings, inspect line numbers, and identify the named human reviewer.

• Turning a lengthy Markdown code review into HTML
• Reading code changes beside review comments
• Jumping directly to findings by severity

4人の異なる専門家ペルソナ（20年ベテランエンジニア、TDDエキスパート、Clean Codeエキスパート、バグハンター）で ソースコードを批判的にレビューするスキル。設計判断、テスト容易性、可読性、バグ検出の観点から コードの問題を検出し、改善提案を行う。Python/JavaScriptに対しては追加のチェックポイントを適用。 バグハンターは状態遷移、例外パス、依存関係、非同期競合に特化し、本番環境での問題を事前に検出する。 Use when reviewing source code from multiple expert perspectives to find design flaws, testability issues, code quality problems, and runtime bugs. Triggers: "critical code review", "multi-persona code review", "expert code review", "code quality assessment", "find bugs".

The English summary is being prepared. Showing the original description.

Checks LazyCodex and Codex CLI installations against current source code, inspecting versions, settings, plugin files, and runtime behavior. Produces an evidence-backed health report with suggested fixes while leaving the installed setup unchanged.

• Diagnosing unexpected behavior after an update
• Checking configuration and plugin files
• Auditing differences from current source code

Review code changes with several independent reviewers working in parallel, then receive organized findings. Request a quick or thorough review, choose to hand off fixes, or run without interaction when another workflow or CI job initiates the review.

• Review code changes from multiple independent perspectives
• Choose a quick or thorough review
• Receive findings with fixes handed off

5つの専門エージェント（backend-reviewer, frontend-reviewer, test-reviewer, security-reviewer, ux-reviewer）がチームでコードレビューするスキル。 git diff ベースで変更ファイルを検出し、各専門家が並列でレビューして 統合レポート（Markdown）を docs/reviews/ に出力する。 Use when: コードレビューしたい、変更をレビュー、レビューチーム、 チームレビュー、実装をチェック、品質チェック。 Triggers: "レビュー", "review", "コードレビュー", "code review", "チームレビュー", "team review", "変更をチェック", "品質チェック"

The English summary is being prepared. Showing the original description.

Review Git changes with the ocr command-line tool and a configured AI model. Get line-level findings grouped by severity for working changes, commits, or branch comparisons, with code fixes applied when explicitly requested.

• Reviewing changes before a commit
• Checking a pull request or branch comparison
• Inspecting a specific commit for issues

Delegate coding, analysis, refactoring, or reviews from Claude Code to Codex CLI. The skill explains unattended execution, permission settings, output capture, parallel tasks, and independent checks of changed files and test results.

• Delegate implementation while retaining planning responsibility
• Get a second opinion on code changes
• Split independent tasks across separate git worktrees

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

codex exec review を基本に、必要なら codex exec を使ってコード変更のレビューを依頼し、指摘事項を報告する。通常 / 厳しめ (--strict) / 敵対的 (--adversarial、実装を壊しにいく red team) の 3 モードを持つ。「codexでレビューして」「codex-review」「/codex-review」「敵対的にレビューして」で発火。Codex 単体での単独レビュー用途。複数エージェント並行レビューは cross-review、差分ではなくコードベース全体の監査は audit を使う。

The English summary is being prepared. Showing the original description.

Delegate research, coding, and testing from Claude Code to opencode workers. Run independent tasks in parallel with separate Git working directories, combine findings, track token use, and compare solo execution with coordinated workers.

• Delegate a small task to one opencode worker
• Implement independent changes in parallel
• Review a diff from four perspectives

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

Write Chinese code review feedback that clearly distinguishes required fixes, suggestions, and optional advice. Use question and suggestion templates, organize review summaries, and follow guidance for mixed Chinese-English comments and commit messages.

• Writing Chinese review comments with clear priorities
• Rephrasing blunt feedback as questions or suggestions
• Standardizing Chinese-English comments and commit messages

Guide changes to RDD reviewer integrations through a shared Go contract, a common set of processing rules. Define adapter boundaries, validate result handling, and check that runtime migrations preserve existing review outcomes.

• Moving reviewer invocation into a shared Go contract
• Checking that adapters only invoke reviewers and return raw output
• Verifying review outcomes during a runtime migration

Review Git code changes using the CodeRabbit CLI. Receive a summary of the changes and issues ordered by severity, with affected file paths, practical impact, and concrete suggestions for follow-up fixes.

• Reviewing uncommitted code changes
• Checking changes against a base branch
• Organizing quality and security issues by severity

Configure ECC in Claude Code, Codex, or Kimi with a guided setup workflow. It checks the current installation, previews supported changes, requests confirmation, applies them, and verifies the result.

• Installing or updating ECC
• Changing installation scope in Claude Code
• Adjusting ECC hook automation in Claude Code

Create step-by-step code walkthroughs tailored to readers such as new contributors, reviewers, or bug fixers. Produce CodeTour .tour files linked to verified files and line numbers, with explanations of behavior, design choices, and pitfalls.

• Create a code walkthrough for new team members
• Guide reviewers through a PR and its risks
• Trace code involved in a bug or incident

Write JavaScript for n8n Code nodes to aggregate, filter, and transform workflow data. Guidance covers data access, output formats, execution modes, common errors, and performance choices when processing large numbers of records.

• Aggregating and deduplicating multiple records
• Transforming complex API responses
• Fixing data access and return format errors

Delegate coding, analysis, planning, and reviews from Codex to Claude Code through its command-line interface. Capture responses, resume sessions, or run independent tasks in parallel, then verify changed files and test results independently.

• Delegating implementation or refactoring from Codex
• Getting another model's review of code changes
• Continuing delegated work across multiple sessions

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