Reduce a failing test case, script, or input file to the smallest version that still reproduces a bug. Use when the user has a large reproduction and asks to minimize, bisect, or isolate it, or says things like "it stops failing when I remove half the file". Do not use when there is no reliable reproduction yet - help build one first, then minimize it.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Shrink the reproduction until every remaining line is load-bearing. The deliverable is a minimal case plus proof that each removed part was irrelevant.
Before cutting anything, define a command that exits 0 for "bug gone" and non-zero for "bug present" — and run it 3 times on the untouched reproduction. If results vary, the bug is flaky; stop and stabilize the oracle first (fixed seed, pinned versions, retries) or minimization will chase noise.
"x", numbers to 0/1, arrays to one element — reverting any change
the oracle rejects.start: 1,842-line SQL dump, importer crashes
cut 1: drop bottom half → still crashes (keep)
cut 2: drop remaining top half → passes (restore, split)
...
final: 3 lines - a CREATE TABLE and one INSERT with a NUL byte in a varchar
The final report: the 3-line case, the oracle command, and the observation that the NUL byte is the trigger — which is the actual bug report.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Diagnose failing HTTP API calls - 4xx/5xx responses, timeouts, TLS errors, and auth failures - by isolating the fault layer and producing a minimal reproduction. Use when the user reports an API request failing, pastes an HTTP error response or status code, or asks why a request works in one client but not another. Do not use for designing new APIs or for performance tuning of requests that already succeed.
中文简介正在准备中。当前显示原文说明。
Generate or update a CHANGELOG.md from merged commits and pull requests, grouped by change type and written for end users. Use when the user asks to write release notes, update the changelog, or summarize what changed between two versions or tags. Do not use for writing individual commit messages or for API-reference documentation.
中文简介正在准备中。当前显示原文说明。
Apply the team style guide to source files - naming conventions, comment style, and file organization. Use when the user asks to align code with the style guide or clean up naming.
中文简介正在准备中。当前显示原文说明。
Run the project's configured formatter (prettier, black, gofmt, rustfmt) on changed files and fix formatting-only CI failures. Use when the user asks to format code, fix a lint/format CI step, or normalize whitespace and import order. Do not use for logic changes or refactoring.
中文简介正在准备中。当前显示原文说明。
Clean and normalize messy CSV/TSV files - fix malformed rows, inconsistent headers, mixed encodings, stray delimiters, and duplicated records - and deliver a valid, verified file. Use when the user mentions a broken, messy, or malformed CSV, a file a spreadsheet tool refuses to open, or asks to deduplicate or normalize tabular data. Do not use when the deliverable is analysis or a chart rather than a cleaned file, or for Excel-native features like formulas and pivot tables.
中文简介正在准备中。当前显示原文说明。
Does data things.
中文简介正在准备中。当前显示原文说明。