Automated summary
Creates a structured GitHub issue in the gittower/git-flow-next repository following project guidelines.
Strengths
- Automatically checks for duplicates before creating the issue.
- Provides templates tailored to issue type (bug, enhancement, feature).
- Integrates with MCP tools to interact directly with the GitHub API.
Limitations
- Limited to the gittower/git-flow-next repository.
- Requires MCP tools to be configured and available.
- Templates are basic and may not cover all edge cases.
Use this skill when you need to create a well-structured GitHub issue for the git-flow-next project, adhering to team conventions.
Do not use it for other repositories or when you need a custom issue format not covered by the provided templates.
Security analysis
SafeThe skill only uses read, search, and create-issue GitHub MCP tools. No shell execution, data exfiltration, or safety bypass. No risky instructions.
No concerns found
How this analysis is madeExamples
Create a bug issue: [bug] Git merge fails when feature branch has conflictsCreate a feature issue: [feature] Add support for rebase workflowsCreate an enhancement issue: [enhancement] Improve error messages in merge commandname: gh-issue description: Create a GitHub issue following project guidelines argument-hint: <title or description> allowed-tools: Read, Grep, Glob, mcp__github__create_issue, mcp__github__list_issues, mcp__github__search_issues
Create GitHub Issue
Create a new GitHub issue for the gittower/git-flow-next repository following project guidelines.
Instructions
-
Gather Information
- If
$ARGUMENTSis provided, use it as the issue title/description - If no arguments, ask the user for:
- Issue type (bug, enhancement, feature)
- Brief description of the issue
- If
-
Check for Duplicates
- Search existing issues for similar topics
- If potential duplicates found, show them to the user and ask to confirm creation
-
Determine Issue Type and Labels
bug- Something isn't workingenhancement- Improvement to existing featurefeature- New feature requestdocumentation- Documentation improvements
-
Create the Issue
- Use clear, descriptive title (imperative mood: "Add...", "Fix...", "Update...")
- Structure the body with appropriate sections based on type
Issue Body Templates
Bug Report
## Description
<Clear description of the bug>
## Steps to Reproduce
1.
2.
3.
## Expected Behavior
<What should happen>
## Actual Behavior
<What actually happens>
## Environment
- OS:
- Git version:
- git-flow-next version:
Enhancement/Feature
## Description
<Clear description of the enhancement/feature>
## Motivation
<Why is this needed? What problem does it solve?>
## Proposed Solution
<How should this work?>
## Alternatives Considered
<Other approaches considered, if any>
- Report Result
- Show the created issue URL
- Suggest next step:
/analyze-issue <number>to start working on it
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/create-github-issue-mmio71r1/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/create-github-issue-mmio71r1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-github-issue-mmio71r1/download' --output '.skill-downloads/create-github-issue-mmio71r1/SKILL.md.part' && mv '.skill-downloads/create-github-issue-mmio71r1/SKILL.md.part' '.skill-downloads/create-github-issue-mmio71r1/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Grep, Glob, mcp__github__create_issue, mcp__github__list_issues, mcp__github__search_issues
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/create-github-issue-mmio71r1/SKILL.md' && test -s '.skill-downloads/create-github-issue-mmio71r1/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/gh-issue' && cp -R '.skill-downloads/create-github-issue-mmio71r1' '.claude/skills/gh-issue'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/create-github-issue-mmio71r1'openskills read 'create-github-issue-mmio71r1'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/create-github-issue-mmio71r1/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.