Github issue
Create a GitHub issue from context or conversationFrom its SKILL.md
npx -y skills add eddmann/agent-toolkit --skill github-issueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 294 tokens by cl100k_base, as published. Nobody here has run it
Create a GitHub issue based on provided context or the current conversation.
Title Format
<type>(<scope>): <summary>
typeREQUIRED:feat,fix,docs,refactor,perf,test,chorescopeOPTIONAL: affected area (e.g.,api,auth,ui)summaryREQUIRED: concise description, under 80 chars total
Body
Include relevant sections only:
- Summary - brief overview
- Description - detailed explanation
- Steps to reproduce - if it's a bug
- Expected behavior - what should happen
- Code snippets / error messages - if applicable
Steps
- If no context is provided, extract it from the current conversation (bugs, features, errors discussed).
- Draft a title and body. Present to the user for approval.
- Iterate if the user requests changes.
- ONLY after approval, create with
gh issue create:gh issue create --title "type(scope): summary" --body "$(cat <<'EOF' Body content here... EOF )" - Report the issue URL.
Notes
- Do NOT create the issue until the user explicitly approves.
- Use the current working directory's git repository.
- Format code and errors properly in markdown.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.