메뉴
Reproduce AFL++ fuzz crashes from GitHub Actions. Use when user provides a GitHub Actions fuzz run URL and wants to reproduce and analyze the crash locally.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/dragonflydb/dragonfly --skill reproduce-fuzz-crash명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | reproduce-fuzz-crash |
| description | Reproduce AFL++ fuzz crashes from GitHub Actions. Use when user provides a GitHub Actions fuzz run URL and wants to reproduce and analyze the crash locally. |
| argument-hint | <github-actions-run-url> |
| allowed-tools | Bash, Read, Grep, Glob, Write |
Given a GitHub Actions fuzz run URL, download crash artifacts, triage them
with fuzz/triage_crashes.sh, and produce a crash analysis report.
Input: $ARGUMENTS — a GitHub Actions run URL like:
https://github.com/dragonflydb/dragonfly/actions/runs/22906484769
or with query params like ?pr=6855.
Extract owner/repo and run_id from the URL.
https://github.com/{owner}/{repo}/actions/runs/{run_id}[?...]
Strip any query parameters from run_id.
List crash artifacts via the GitHub API, then download each as a .zip directly:
IMPORTANT: Run each command as a separate Bash tool call (no && chaining)
to ensure auto-approval works with the user's permission patterns.
# List artifacts — filter for names containing "crash"
gh api repos/{owner}/{repo}/actions/runs/{run_id}/artifacts
-p /tmp/fuzz-repro-{run_id}
gh api repos/{owner}/{repo}/actions/artifacts/{artifact_id}/zip > /tmp/fuzz-repro-{run_id}/<artifact-name>.zip
This gives real .zip files that the triage script can consume directly.
If no crash artifacts are found, report that the run has no crash artifacts and stop.
Note: there may be duplicate artifact names (same name, different IDs) from retried jobs. Download the most recent one (highest artifact ID).
Infer the protocol mode from the artifact name:
memcacherespCheck if the debug binary already exists and runs:
./build-dbg/dragonfly --version
Only build if the binary doesn't exist or fails to run:
ninja -C build-dbg dragonfly
If build-dbg doesn't exist, run ./helio/blaze.sh first.
For each zip file, run:
./fuzz/triage_crashes.sh ./build-dbg/dragonfly <mode> /tmp/fuzz-repro-{run_id}/<artifact-name>.zip
Capture the full output.
Parse the triage output for confirmed crashes. For each confirmed crash:
Print a structured report:
## Fuzz Crash Report
**Run**: {url}
**Artifacts**: {number} crash(es) found
---
### Crash NNNNNN
**Reproduced**: Yes / No (false positive)
**Signal**: SIGABRT (6) / SIGSEGV (11) / etc.
**Stack trace**:
\```
<stack trace from triage output>
\```
**Analysis**:
<1-3 sentences explaining the likely root cause based on the stack trace,
the assertion message, and the crash input. Identify the source file and
line number. Suggest what to investigate.>
--restricted_commands flags to avoid false positives from
commands like DEBUG SLEEP that the fuzzer might generate./tmp/fuzz-repro-{run_id}/ — the user may want to inspect it.gh run download fails with permissions, suggest the user authenticate
with gh auth login.