Write or revise a software issue so maintainers can understand the problem, reproduce it, and see the desired outcome. Follow the repository’s template, remove distracting detail, and verify claims before publishing or updating an issue.
This skill should be used when the user asks to "create an issue", "file a bug", "report a problem", "rewrite an issue", or "improve an issue title or body".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
An issue describes a problem or missing capability. A PR describes a proposed change. Keep their writing rules separate. For PRs, use create-pr.
Use a concise statement of the problem, naming the affected behavior. Do not use an imperative change request such as "Fix", "Add", "Enable", or "Keep" as the default.
Follow the repository's issue template and the user's requested format. Otherwise use:
## Problem
One or two sentences naming the failure and its effect.
## Reproduction
1. The relevant setup or version.
2. The smallest steps that demonstrate the problem.
## Current behavior
What was observed, with a short error or result when useful.
## Desired behavior
The outcome the reporter needs.
For a missing feature, reproduce the current workflow that exposes the gap. If the problem was not reproduced, say so instead of inventing steps or results. Add environment details, evidence, or a proposed approach only when they help a maintainer act. Keep a possible implementation separate from the desired outcome.
Remove repeated explanations, promotional claims, conversation history, full diagnostic dumps, and details that do not help reproduce or resolve the issue. A few useful sections are better than a long narrative or a checklist of every investigation step.
Inspect repository guidance and templates, search for an existing issue, and verify the claims before publishing. When revising, read the current issue and preserve useful attachments, links, and user edits. Do not expand an issue's scope without user direction.
Use gh issue create or gh issue edit with --title and --body-file. Read back the
published title and body. Link related PRs, but use a closing reference only when the PR
addresses the issue's complete desired outcome.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Format responses for readers who benefit from concise, visible steps and low-friction starts. It puts the answer first, breaks work into short numbered actions, tracks progress, and adds brief educational notes around code changes while keeping secondary details separate.
Plan and assess how AI assistants discover and recommend a product to buyers who have not heard of it. Organize buyer questions, review answers and cited sources, identify content or access gaps, and define a repeatable way to measure visibility and customer outcomes.
Use this skill to automate browser tasks such as opening websites, reading page content, clicking controls, filling forms, signing in, extracting data, and taking screenshots. It explains a snapshot-based workflow for interacting with pages and handling tabs and waits.
Build, debug, or review applications built with Cloudflare’s Agents SDK and the `agents` package. It covers agent state, routing, chat, scheduled and durable work, and integrations, while consulting current Cloudflare documentation for implementation details.
Use this skill to plan and build web interfaces with a visual direction tied to the project. It guides choices for color, typography, layout, motion, and interface text, then encourages a review against the brief so the result feels deliberate and specific.
Standardize web app sign-in and account flows with shared session rules, email and Google login adapters, and an optional auth panel. Use the guidance to simplify signup, recovery, and return navigation while keeping native and TV integrations clearly identified as pending validation.