← ClaudeAtlas

file-github-issuelisted

File a GitHub issue as a Bug, Feature or Task, written in plain language anyone can understand, with Type, Title, Description, Pre-condition, Steps to Reproduce, Actual, Expected and Evidence. Captures before/after screenshots and a step-by-step GIF (or uses the user's own files), uploaded to a secret gist in the user's own GitHub account. Use this skill whenever the user asks to file, create, open, raise, log or report an issue, bug, feature request, task or ticket on GitHub, for example "file the issue", "file this in GitHub", "open an issue for this", "log this bug", "add a feature request", "create a task for this" or "make a ticket for this". Also use it when the user describes something broken, wanted or needing to be done and wants it recorded, or shares a screenshot or recording of a problem, even if they never say "GitHub issue". If it was already discussed earlier in the conversation, start from that instead of asking again.
subin-shk/file-github-issue · ★ 0 · Data & Documents · score 72
Install: claude install-skill subin-shk/file-github-issue
# File a GitHub issue in plain language The goal is an issue that a developer can act on without asking questions, and that a manager, tester or customer can read and understand. The person filing it may not be technical, so speak to them simply too. ## 1. Collect the facts Work out what you already know from the conversation first. Ask only for what is missing, in short, friendly questions, a few at a time rather than a long form. You need: - **Which repository** (`owner/repo`). If you're inside a git repo, `gh repo view --json nameWithOwner,isPrivate` tells you. Confirm it with the user rather than guessing. - **Which type it is: Bug, Feature or Task.** Decide this from what they describe rather than asking, and show it in the preview so they can change it: | Type | Choose it when… | Examples | |---|---|---| | **Bug** | Something that should already work is broken, wrong or missing | "The Save button does nothing", "Prices show in the wrong currency" | | **Feature** | They want something new, or an existing thing made better, easier or clearer | "Add a dark mode", "Let me export to Excel", "The error message is confusing" | | **Task** | Work that needs doing where nothing is broken and the product itself doesn't change for users | "Update the help page screenshots", "Renew the SSL certificate", "Translate the settings page" | The quickest test: *does it work the way it was meant to?* No → **Bug**. Yes, but they want it to do more or work differently → **Fe