Run any Skill in Manus with one click

issue-writer

Stars23

Forks4

UpdatedJune 9, 2026 at 09:14

Draft GitHub issues for nubank/clojuredocs. Use when filing bugs, enhancements, or feature requests. Use when turning Slack threads, conversation context, feature proposals, or bug reports into well-structured issues.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

nubank

nubank/clojuredocs

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	issue-writer
description	Draft GitHub issues for nubank/clojuredocs. Use when filing bugs, enhancements, or feature requests. Use when turning Slack threads, conversation context, feature proposals, or bug reports into well-structured issues.

Issue Writer

Draft GitHub issues for nubank/clojuredocs that diagnose problems rather than prescribe solutions.

When to use

Turning a Slack thread into an issue
Filing a bug, enhancement, or feature request
Converting a rough description or conversation into a structured issue

Procedure

Classify. Determine the issue type (bug, enhancement, feature). If the input is not an issue at all (e.g., a general question, support request, or discussion topic), tell the user it does not map to a GitHub issue and suggest an alternative (e.g., Slack channel, GitHub Discussion). Ask one clarifying question only if the type or user-facing impact is genuinely ambiguous.
Verify. If the user mentions a URL or file path, fetch or read it to confirm the claim before drafting.
Pick the template. Use the matching issue template (bug, enhancement, or feature). Load docs/github-templates/issue-writing-guide.md for section guidance and examples.
Draft. Write the issue following the template structure: Problem, Demonstration/Steps to Reproduce, Context, and References. Omit sections that don't apply.
Deliver. Present the draft in chat. Save as a .md file only if the user asks to commit it.

Note: Father Watson diagnostic questions (What do we know? What do we need to know? Where are we? Where are we going?) belong in the PR description template, not in issues.

Key constraints

Frame, don't solve — no implementations, function names, or code changes
No Acceptance Criteria, Risks & Mitigations, or Implementation Steps sections
Calm, technical prose — no emoji, exclamation points, or hype language
Terseness is a virtue — omit sections that don't apply, don't pad

More from this repository

same repository

narrate

nubank/clojuredocs

Reframe the current work session as a short narrative for a human, fitting a classic story arc (hero's journey, man in a hole, three-act, Vonnegut shapes, story circle). Use for a recap, retro, demo, or changelog where a memorable story beats a status list. The arc shapes emphasis; the facts stay real; keep it brief.

2026-07-0123

grill-me

nubank/clojuredocs

Alignment-first interview before building. Claude interviews you to surface requirements, constraints, edge cases, and acceptance criteria, then writes a short plan/PRD to disk that survives a /clear. Use at the start of any non-trivial task, before writing code.

2026-07-0123

handoff

nubank/clojuredocs

Write a structured state-of-work note to disk so you can /clear and resume in a fresh context instead of using /compact. Use at phase boundaries or when the session is long enough that reasoning quality is degrading (~100K tokens, the "smart zone" ceiling).

2026-07-0123

ratchet

nubank/clojuredocs

Harden an informal finding, convention, or manual check into progressively more deterministic enforcement: LLM → REPL → Library → Enforcement. Use when you catch yourself repeating a check by hand, or relying on the model to "remember" a rule.

2026-07-0123

name	issue-writer
description	Draft GitHub issues for nubank/clojuredocs. Use when filing bugs, enhancements, or feature requests. Use when turning Slack threads, conversation context, feature proposals, or bug reports into well-structured issues.

Issue Writer

Draft GitHub issues for nubank/clojuredocs that diagnose problems rather than prescribe solutions.

When to use

Turning a Slack thread into an issue
Filing a bug, enhancement, or feature request
Converting a rough description or conversation into a structured issue

Procedure

Classify. Determine the issue type (bug, enhancement, feature). If the input is not an issue at all (e.g., a general question, support request, or discussion topic), tell the user it does not map to a GitHub issue and suggest an alternative (e.g., Slack channel, GitHub Discussion). Ask one clarifying question only if the type or user-facing impact is genuinely ambiguous.
Verify. If the user mentions a URL or file path, fetch or read it to confirm the claim before drafting.
Pick the template. Use the matching issue template (bug, enhancement, or feature). Load docs/github-templates/issue-writing-guide.md for section guidance and examples.
Draft. Write the issue following the template structure: Problem, Demonstration/Steps to Reproduce, Context, and References. Omit sections that don't apply.
Deliver. Present the draft in chat. Save as a .md file only if the user asks to commit it.

Note: Father Watson diagnostic questions (What do we know? What do we need to know? Where are we? Where are we going?) belong in the PR description template, not in issues.

Key constraints

Frame, don't solve — no implementations, function names, or code changes
No Acceptance Criteria, Risks & Mitigations, or Implementation Steps sections
Calm, technical prose — no emoji, exclamation points, or hype language
Terseness is a virtue — omit sections that don't apply, don't pad