- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add kajisho5/ffmpeg-skill --skill sibling-sweep -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add kajisho5/ffmpeg-skill --skill sibling-sweep -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add kajisho5/ffmpeg-skill --skill sibling-sweep -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add kajisho5/ffmpeg-skill --skill sibling-sweep -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/kajisho5/ffmpeg-skill/tree/HEAD/.claude/skills/sibling-sweepपब्लिशर से
A report from outside names one tool and one input. It is almost never the only
place the defect lives, and the reporter found it because nobody inside thought
to look. #437 named insert.py and an odd-sized JPEG; the same odd frame also
broke caption.py and crashed stabilize.py on a video, which nobody had
reported. #436 named --position top; the documented example in --help used
that exact flag and had never worked.
So a fix for the reported line is half the job. The other half is the sweep, and it happens before the fix is written, because the siblings decide where the fix belongs (one shared helper, or one tool).
Reproduce the report as written, on the local FFmpeg. If it does not
reproduce, check the fixture before the tool: FFmpeg sources round sizes,
drop tags and pick pixel formats on their own (the color source turns
629x1400 into 628x1400 for 4:2:0). Build the input another way and assert its
properties with probe.py first.
Name the class. Write one sentence that does not mention the reported tool. The usual classes here:
Sweep. python3 tests/sweep.py INPUT --baseline PLAIN prints only the
tools whose result differs from a plain clip's. Vary the property, not only
the tool: if the report is an odd JPEG, also try an odd PNG, an odd video,
an odd size in each of width and height. For a flag, run every choice of the
flag, not the one reported.
Sort the rows. For each differing row, read docs/design-decisions.md:
kind: input and a hint that names the way out is usually
a decision: leave it, and say in the PR that it was seen;kind: ffmpeg, an assertion, "Nothing was written", or a completed run
whose output is wrong is a sibling.A row that matches the baseline proves less than it looks: the sweep compares
what each tool said, and deletes what it wrote. A defect in the pixels or
the sound with an honest-looking result (the #436 kind: completed,
verified: true, text in the wrong place) leaves every row equal. When the
class is "the output is wrong" rather than "the run fails", run the tools the
class can reach yourself and measure the output (a bounding box, a frame
hash, check.py --compare, a loudness reading), matching rows included.
Decide where the fix goes. Two or more siblings through one helper: fix the helper. Siblings with separate causes: fix the reported one here and file the others in one issue titled by the class, with the sweep rows pasted in.
Pin the class, not the report. The regression test iterates the property (all seven positions, both odd axes, both paths), and asserts the fixture before the tool.
Say what was swept in the PR body under "Siblings": the class sentence, the command, the rows that differed, and which were fixed, filed or decided. "None found" needs the command that found none.
tests/sweep.py prints what each tool said. A row is a
question for design-decisions, not a bug by itself.join, sync, multicam, broll, render, batch, sequence, grid,
insert, report and background by hand when the class can reach them.Turn one reported defect in ffmpeg-skill into the full list of places the same thing happens — naming the defect's class (an input property, a shared step, a convention that differs between two code p
---name: sweeping-defect-siblingsdescription: Turn one reported defect in ffmpeg-skill into the full list of places the same thing happens — naming the…---# .claude/skills/sibling-sweep/SKILL.mdओवरव्यू
Turn one reported defect in ffmpeg-skill into the full list of places the same thing happens — naming the defect's class (an input property, a shared step, a convention that differs between two code paths, an FFmpeg-version behaviour), sweeping every tool with tests/sweep.py and a path-parity probe, separating decided refusals from real siblings, and landing the fix with one regression test per class rather than per report. Use whenever an issue or PR comment reports a bug in this repository, before writing the fix, and again when triaging an external review or audit.
FAQ
पब्लिशर से .claude/skills/sibling-sweep/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/kajisho5/ffmpeg-skill पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।