“errors”的搜索结果

Build an MCP integration skill using a template that reads server-specific reference notes before calling tools. The Sentry example gathers unresolved errors, groups them by likely root cause, and produces a report with investigation suggestions.

中文简介正在准备中。当前显示英语简介。

• Design a skill that integrates with an MCP server
• Document server-specific query pitfalls
• Group Sentry errors by likely root cause

Build React interfaces that clearly handle loading, errors, empty results, and submissions. Use examples and checklists to keep existing data visible during refetching, offer retry actions, and disable buttons while asynchronous operations are running.

中文简介正在准备中。当前显示英语简介。

• Keeping existing data visible during refetching
• Adding visible errors and retry actions
• Showing guidance when lists or search results are empty

Investigate code errors through a structured process using reproduction steps, logs, and testable explanations. The workflow guides fault isolation, fixes, and follow-up checks, with common error patterns for Python, JavaScript/TypeScript, and Bash/Zsh.

中文简介正在准备中。当前显示英语简介。

• Investigating an error using logs and reproduction steps
• Finding why code broke after a recent change
• Troubleshooting common shell script errors

Upgrade an existing .NET 8 project to .NET 9 by addressing build errors and compatibility changes. Update related packages, containers, and build pipelines, then verify the migration with clean builds and tests.

中文简介正在准备中。当前显示英语简介。

• Upgrading a project from net8.0 to net9.0
• Resolving new build errors and warnings after upgrading
• Reviewing ASP.NET Core and EF Core behavior changes

Move existing .NET 9 projects to .NET 10 by updating project settings and dependencies, fixing build errors, and reviewing behavior changes. Includes CI and Docker updates, followed by builds, tests, and security checks.

中文简介正在准备中。当前显示英语简介。

• Upgrading an existing .NET 9 project to .NET 10
• Fixing build errors and warnings after an SDK upgrade
• Reviewing ASP.NET Core and EF Core behavior changes

Diagnose and fix .NET MAUI development environment problems involving SDKs, Java, Android tools, and platform requirements. The skill discovers required versions from NuGet metadata and checks the environment again after each fix.

中文简介正在准备中。当前显示英语简介。

• Setting up a .NET MAUI development environment
• Investigating missing SDK or JDK build errors
• Checking the environment after SDK or OS updates

Diagnose MSBuild failures from an existing binary build log. Inspect errors, settings, project references, and execution details to explain failures that console output alone does not clarify, including failures across multiple projects.

中文简介正在准备中。当前显示英语简介。

• Investigating build errors with unclear console output
• Tracing cascading failures across multiple projects
• Checking MSBuild target execution order

Investigate code with the lsp tool, which uses a language server to understand names, imports, and types. Find definitions and usages, inspect signatures and file outlines, and check compiler or type errors after edits.

中文简介正在准备中。当前显示英语简介。

• Finding where a function or variable is defined
• Tracing symbol usages across imports and aliases
• Reading type signatures and documentation

Investigate local Rust services by starting the crate’s executable with debug logging and following its log output. Use the recorded messages to examine startup problems, runtime behavior, and errors while discussing findings with the agent.

中文简介正在准备中。当前显示英语简介。

• Investigating service startup problems
• Checking runtime behavior through logs
• Examining errors with an agent

Check and improve existing English LaTeX papers, from compilation errors and bibliography issues to grammar, figures, tables, and pseudocode. Receive focused review comments and suggested fixes, with checks tailored to specific sections or publication venues.

中文简介正在准备中。当前显示英语简介。

• Diagnosing LaTeX compilation and bibliography errors
• Polishing grammar and shortening dense sentences
• Checking figures, tables, and pseudocode before submission

Investigate code errors through a structured process using reproduction steps, logs, and testable explanations. The workflow guides fault isolation, fixes, and follow-up checks, with common error patterns for Python, JavaScript/TypeScript, and Bash/Zsh.

中文简介正在准备中。当前显示英语简介。

• Investigating an error using logs and reproduction steps
• Finding why code broke after a recent change
• Troubleshooting common shell script errors

Choose and interpret models for panel data, which tracks the same firms, people, or countries over time. Use Python, R, or Stata examples to compare fixed and random effects, check assumptions, and select standard errors.

中文简介正在准备中。当前显示英语简介。

• Choosing between fixed and random effects
• Estimating entity and time effects together
• Selecting standard errors for correlated observations

Plan, run, and interpret linear regression with guidance on model choices, diagnostic checks, and reporting. Python, R, and Stata examples help examine coefficients, assess assumptions, and choose standard errors that account for different error patterns.

中文简介正在准备中。当前显示英语简介。

• Specify a regression model for an empirical study
• Check residuals and correlations among explanatory variables
• Choose robust or clustered standard errors

Collect unresolved work that needs human judgment from configured pull requests, issues, feedback, errors, and delivery signals. Group related problems into a decision queue with source links, supporting evidence, and visible gaps in coverage.

中文简介正在准备中。当前显示英语简介。

• Reviewing work that still needs a human decision
• Grouping recurring errors and user concerns
• Checking pull requests awaiting review or approval

Review and fix concurrency issues in Swift 6.2+ code, including compiler errors and unsafe shared data. Apply actor isolation, which controls access to state, and separate UI updates from background work while preserving existing behavior.

中文简介正在准备中。当前显示英语简介。

• Fixing Swift concurrency compiler errors
• Reviewing shared data for race conditions
• Separating UI updates from heavy background work

XML sitemap audit — find and fix the sitemap problems that quietly waste crawl budget and slow indexing. Discovers the sitemap (robots.txt, /sitemap.xml, sitemap index), validates structure and size limits, and cross-checks the URLs it lists against reality: non-200 / redirected / noindex / canonicalized-away URLs that shouldn't be in a sitemap, plus indexable pages that are missing from it. Reviews lastmod accuracy, sitemap-index organization, and robots.txt reference. Use this skill whenever the user asks about sitemaps, sitemap errors in Search Console, "sitemap couldn't fetch / has errors", crawl budget, pages not getting indexed, or whether their sitemap is clean. Trigger on: "sitemap", "sitemap.xml", "XML sitemap", "sitemap errors", "sitemap audit", "couldn't fetch sitemap", "crawl budget", "pages not indexed sitemap", "sitemap index", "lastmod", "robots.txt sitemap", or any sitemap/crawl-coverage question. For a full-site SEO audit use /seo-analysis; for broken links use /broken-link-checker.

中文简介正在准备中。当前显示原文说明。

[omh] Hidden or swallowed errors suspected: find swallowed errors, unsafe fallbacks, hidden UI/runtime failures, and missing propagation before they become false green status. Use when the user says: failure-signal-audit, failure signal audit, silent failure, silent failures, silent failure hunter, swallowed error, swallowed errors, empty catch.

中文简介正在准备中。当前显示原文说明。

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).

中文简介正在准备中。当前显示原文说明。

Diagnose and fix common Apollo.io API errors. Use when encountering Apollo API errors, debugging integration issues, or troubleshooting failed requests. Trigger with phrases like "apollo error", "apollo api error", "debug apollo", "apollo 401", "apollo 429", "apollo troubleshoot".

中文简介正在准备中。当前显示原文说明。

Diagnose and fix common Anima SDK design-to-code errors. Use when encountering Figma token errors, code generation failures, node not found issues, or output quality problems. Trigger with: "anima error", "anima not working", "anima debug", "figma to code error".

中文简介正在准备中。当前显示原文说明。

Diagnose and fix Anthropic Claude API errors by HTTP status code. Use when encountering API errors, debugging failed requests, or troubleshooting authentication, rate limiting, or input validation issues. Trigger with phrases like "anthropic error", "claude api error", "fix anthropic 429", "claude not working", "debug claude api".

中文简介正在准备中。当前显示原文说明。

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).

中文简介正在准备中。当前显示原文说明。

Surfaces PAC CLI upload errors and Dataverse async operation errors, pattern-matches against a known failure catalog, and optionally auto-fixes identified issues. Use when asked to: "diagnose deployment", "debug deployment", "deployment failed", "show deployment errors", "fix deployment issues", "show upload logs", "why did my deploy fail", or "troubleshoot upload".

中文简介正在准备中。当前显示原文说明。

Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue, Svelte, Angular, Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET, React Native, Flutter), (2) Wire up uncaught exception and unhandled promise rejection capture, (3) Configure session replay for errors, (4) Upload source maps for readable stack traces, (5) Report releases and environments, (6) Capture custom errors/messages. Triggers: "add error tracking", "add sentry", "track exceptions", "report errors", "temps error tracking", "wire up error monitoring".

中文简介正在准备中。当前显示原文说明。