# Create Issue With Websearch

Create a GitHub issue from a vague idea by thoroughly researching the topic on the web...

- Repository: https://github.com/dyoshikawa/rulesync (1577 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add dyoshikawa/rulesync --skill create-issue-with-websearch -g -a claude-code -y`
Codex: `npx skills add dyoshikawa/rulesync --skill create-issue-with-websearch -g -a codex -y`
Cursor: `npx skills add dyoshikawa/rulesync --skill create-issue-with-websearch -g -a cursor -y`
Gemini CLI: `npx skills add dyoshikawa/rulesync --skill create-issue-with-websearch -g -a gemini-cli -y`

## Description

Create a GitHub issue from a vague idea by thoroughly researching the topic on the web to sharpen the specification before filing

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

topic = the user's request

Use this skill when the user only has a rough, fuzzy idea and needs heavy web research to clarify the target specification before creating an issue. If the user already has a concrete, well-scoped task in mind, use the `create-issue` skill instead.

## Step 1: Gather the Initial Idea

Receive the topic from `topic` or the user's description.

If the input is very sparse, ask the user just enough to anchor the research:

- What is the rough area or goal? (e.g., a tool to support, a feature to add, a behavior to change)
- Why do they want it, what problem or limitation triggered the idea?
- Any hard constraints known up front (must/must-not, scope boundaries)?

Do not push for full specification details at this stage. The point of this skill is to resolve the unknowns through research, not to force the user to resolve them manually.

## Step 2: Research the Topic on the Web

Investigate the topic thoroughly using `WebSearch` and `WebFetch`. The goal is to raise the resolution of the specification until concrete, defensible design decisions become possible.

Look for, as applicable to the topic:

- Official documentation of any tool, standard, protocol, or API involved, prefer primary sources over blog posts.
- File formats, configuration schemas, naming conventions, and default locations used by the target tool(s).
- Feature support matrices: project vs. global scope, supported file types, known limitations.
- Recent changes, deprecations, or pre-release behavior that might affect the design.
- Prior art: how similar tools or competing implementations solve the same problem.
- Existing discussions (GitHub issues, release notes, RFCs) that reveal open questions or community expectations.

Guidelines while researching:

The rest: https://github.com/dyoshikawa/rulesync/blob/HEAD/.rulesync/skills/create-issue-with-websearch/SKILL.md