# Reproduce

Reproduce a cloudflare/agents GitHub issue by scaffolding a minimal Agents/Worker...

- Repository: https://github.com/cloudflare/agents (5931 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add cloudflare/agents --skill reproduce -g -a claude-code -y`
Codex: `npx skills add cloudflare/agents --skill reproduce -g -a codex -y`
Cursor: `npx skills add cloudflare/agents --skill reproduce -g -a cursor -y`
Gemini CLI: `npx skills add cloudflare/agents --skill reproduce -g -a gemini-cli -y`

## Description

Reproduce a cloudflare/agents GitHub issue by scaffolding a minimal Agents/Worker project and deploying it to a temporary Cloudflare account, then report findings back on the issue.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

The current user message contains an `<agent-think-run>` envelope with
`repository`, `issue`, `instruction`, `requested-by`, and (when available)
`trigger-comment-id`.
Use those values exactly. Never infer or substitute another target from examples,
workspace contents, GitHub searches, or concurrent issues. If the envelope or a
required field is absent, stop without cloning/editing/posting and return a
structured skipped result. When `trigger-comment-id` is present, your first
container action is the liveness reaction:

```bash
gh api repos/<repository>/issues/comments/<trigger-comment-id>/reactions \
  -f content=rocket
```

Reproduce the bug end-to-end and post your findings as an issue comment.

The instruction is the free-form text the user typed after `@agent-think` (it
may be empty). Treat it as an extra hint from the triggering user, e.g. additional reproduction steps, a specific version, or a pointer to the
suspect area. Let it guide your reproduction, but the issue itself remains the
source of truth.

All `gh`, `git`, `npm`, `curl`, and `wrangler` commands must run on the
`container` backend (`bash({ command, backend: "container" })`), the `shell`
backend has no real binaries or network. `gh` is already authenticated as the
app; use it directly (no token handling).

## 0. Clone the repo

Clone the target repo directly under `/workspace` using its repository name
(`cloudflare/agents` → `/workspace/agents`):

```bash
REPO_DIR="/workspace/$(basename <repo>)"
if [ ! -d "$REPO_DIR/.git" ]; then
  git clone --depth=1 https://github.com/<repo>.git "$REPO_DIR"
fi
```

## 1. Understand the issue

```bash
gh issue view <issueNumber> --repo <repo> --json title,body,labels,comments
```

Read it carefully. Extract:

- the **observed behavior** (the bug),
- the **expected behavior**,
- any **"To Reproduce" steps**, code snippets, versions, or stack traces.

The rest: https://github.com/cloudflare/agents/blob/HEAD/agent-think/skills/reproduce/SKILL.md