Menu
Use this skill when creating GitHub or GitLab issues; searches for duplicates before filing.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use this skill when deploying a static site to GitHub Pages — configures base path, Actions workflow, and Pages source.
Use this skill when a published-package change needs a changeset (monorepos supported).
Use this skill when auditing a SKILL.md for structure, quality, and security before installing or committing.
Use this skill when the user asks to create a new agent skill — scaffold, audit, and link into detected agents.
Use this skill when looking for curated skill recommendations from awesome lists, with exact install commands.
Use this skill when a PR fails security or vulnerability checks (audit, CVE, Dependabot, Snyk, or advisory blocks).
| name | create-issue |
| description | Use this skill when creating GitHub or GitLab issues; searches for duplicates before filing. |
Creates a well-formed bug report or feature request on the appropriate issue tracker, after checking for existing similar issues to avoid duplicates.
Use when asked to create an issue, file a bug, open a feature request, or report a problem.
Detect the platform from the git remote URL:
| Remote pattern | Platform | CLI tool |
|---|---|---|
github.com | GitHub | gh |
gitlab.com or self-hosted GitLab | GitLab | glab |
bitbucket.org | Bitbucket | gh with Bitbucket extension or browser |
git remote get-url origin
If the user has not already provided them, ask for:
Do not ask for information the user has already provided.
For bug reports, collect the system and package information that will help maintainers reproduce and triage the issue.
Include relevant details such as:
Prefer discovering exact versions from the local environment or repo when possible instead of asking the user. If the issue is a feature request, include environment details only when they materially affect the request.
Before creating, search for duplicates. Use the title keywords and key terms from the description.
GitHub:
gh issue list --repo <owner>/<repo> --state all --search "<keywords>" --limit 10
GitLab:
glab issue list --all --search "<keywords>"
Search at least twice with different keyword combinations (e.g. full title, then core noun/verb only) to maximize recall.
Present any matches to the user:
If a match is found and the user confirms it is the same issue, stop — do not create a duplicate. Instead, provide the URL of the existing issue and suggest the user add a comment or reaction if they want to signal the issue affects them too.
If no duplicates found (or user confirms none match), summarize what will be created:
Ask for confirmation before proceeding.
GitHub:
gh issue create \
--repo <owner>/<repo> \
--title "<title>" \
--label "<bug|enhancement>" \
--body "$(cat <<'EOF'
## Description
<description>
## Steps to Reproduce (bugs only)
1. ...
## Expected Behavior
<expected>
## Actual Behavior
<actual>
## Environment
- OS: ...
- Architecture: ...
- Runtime: ...
- Package manager: ...
- Affected package: ...
- Related toolchain/compiler: ...
## Notes
<version split, container/WSL/CI context, or other triage-relevant details>
EOF
)"
GitLab:
glab issue create \
--title "<title>" \
--label "<bug|feature>" \
--description "<body>"
For feature requests use label enhancement (GitHub) or feature (GitLab). For bugs use label bug.
If labels don't exist in the repo, omit the --label flag rather than erroring.
After creation, output the issue URL so the user can navigate to it directly.
bug, enhancement)