draft-issue-to-external-repository
Draft a GitHub issue targeting a third-party repository (outside this project's owner). Researches the target repo's conventions and the topic in depth, iterates with the user on scope and tone, and produces a final body saved to tmp/external-repository-issues/*.md for the user to post manually when gh auth lacks permission on the target.
Profile →npx skills add dyoshikawa/rulesync --skill draft-issue-to-external-repository --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
arguments = the user's request Parse `arguments` as: - `target_repo`: the target repository in `owner/repo` form (or a URL) - `intent`: the rough idea the user wants to propose (may be vague — this skill is designed to sharpen it) If `target_repo` is not provided, ask the user which repository to file against. If `intent` is not provided, ask the user what they want to propose. This skill is for proposing a change to a repository **we do not own**. When the target is a repo under the user's own owner, prefer `create-issue` or `create-issue-with-websearch` instead. ## Step 1: Inspect the Target Repository Before drafting anything, understand the target repo's conventions. Run in parallel: - `gh repo view <owner/repo> --json description,url,defaultBranchRef,primaryLanguage,latestRelease` - `gh issue list --repo <owner/repo> --limit 20 --state all --json number,title,labels,state` — read recent titles to learn the house style (prefix tags like `[FEATURE]`, casing, length). - `gh api repos/<owner/repo>/contents/.github/ISSUE_TEMPLATE` — list templates. If a feature-request template exists, fetch it with `gh api` or a raw URL and note the required sections plus any auto-applied title pr
- Step 1: Inspect the Target Repository
- Step 2: Research the Topic
- Step 3: Ground the Proposal in This Repo
- Step 4: Align with the User on Scope and Tone
- Step 5: Draft in the Conversation Language First
- Step 6: Translate the Approved Draft to English
- Step 7: Try Posting, Fall Back to Disk
- Step 8: Report
gh issue create --repo <owner/repo> \
What does the draft-issue-to-external-repository skill do?
Draft a GitHub issue targeting a third-party repository (outside this project's owner). Researches the target repo's conventions and the topic in depth, iterates with the user on scope and tone, and produces a final body saved to tmp/external-repository-issues/*.md for the user to post manually when gh auth lacks permission on the target.
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill draft-issue-to-external-repository --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.