Run any Skill in Manus with one click

open-issue

Stars0

Forks0

UpdatedJuly 10, 2026 at 04:05

Drafts and creates a GitHub issue by filling out the right template from .github/ISSUE_TEMPLATE/ based on the type (bug, feature, documentation, task, or question). Use this when the user asks to open/create an issue, report a bug, or record a task/request (e.g. "open an issue for this bug", "create an issue for the new feature", "log this task"). Does not close or comment on existing 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

brayandiazc

brayandiazc/project-starter-template-en-ai

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	open-issue
description	Drafts and creates a GitHub issue by filling out the right template from .github/ISSUE_TEMPLATE/ based on the type (bug, feature, documentation, task, or question). Use this when the user asks to open/create an issue, report a bug, or record a task/request (e.g. "open an issue for this bug", "create an issue for the new feature", "log this task"). Does not close or comment on existing issues.
argument-hint	[title or short description]

Create a well-formed issue using the repository's template.

Look at the available templates in .github/ISSUE_TEMPLATE/ and pick the one that matches the issue type:
- bug_report.md — a defect or incorrect behavior.
- feature_request.md — a new feature or improvement.
- documentation_request.md — something missing or wrong in the docs.
- task.md — an internal work task (chore, refactor, tooling).
- support_question.md — a support question or doubt. If the type is ambiguous from $ARGUMENTS, ask before choosing.
Read the chosen template to learn its required sections and its front matter (title:, labels:, assignees:). Respect that front matter.
Fill in each section using the info from $ARGUMENTS and the conversation context:
- A clear, descriptive title (not generic like "bug").
- Reproduction steps / expected vs. actual behavior for bugs.
- Motivation and acceptance criteria for features and tasks.
- Leave as a prompt (don't invent) any data you don't have: versions, environment, screenshots.
Create the issue with the gh CLI following the template, e.g. gh issue create --title "…" --body "…" --label "…" (or --template <file> for the interactive flow). If there is no remote configured, output the filled issue for the person to paste into GitHub.
Report the URL of the created issue (or the drafted body).

Example: /open-issue login fails with Google on Safari → filled .github/ISSUE_TEMPLATE/bug_report.md, published.

Do NOT invent data you don't have (versions, logs, environment) — leave them as prompts, do NOT create a duplicate issue if an identical one already exists (search first with gh issue list), and do NOT close, edit, or comment on existing issues.

More from this repository

same repository

instantiate

brayandiazc/project-starter-template-en-ai

Instantiates this template into a real project through a guided interview — detects whether the project is new or existing, fills in the placeholders, adapts the docs to the project type, and decides the permissions policy. Use this when someone clones/adopts this template and wants to configure it for their project (e.g. "instantiate this template", "set up this template for my project", "bootstrap the project from this base").

2026-07-100

new-spec

brayandiazc/project-starter-template-en-ai

Scaffolds a new lightweight change spec by copying the spec template directory into a named spec folder. Use this when the user wants to start a spec, plan a change/feature, or create a design doc before implementing (e.g. "spec out the checkout redesign", "create a spec for the new auth flow").

2026-07-100

port-change

brayandiazc/project-starter-template-en-ai

Ports the current branch's change to this template's sibling variants (es/en × with-AI/no-AI) — translates the content, adapts or removes the AI layer depending on the target, and leaves each variant with a PR-ready branch. Use this when a template change must be replicated in the other variants (e.g. "port this change to the Spanish template", "replicate this in the variants").

2026-07-100

release

brayandiazc/project-starter-template-en-ai

Cuts a new version — moves the CHANGELOG's Unreleased section to a dated SemVer version, creates the commit and the tag, and optionally the GitHub release. Use this when someone asks to publish/cut a version or prepare a release (e.g. "cut version 1.2.0", "prepare the release", "publish a new version"). Does not push without confirmation.

2026-07-100

update-template

brayandiazc/project-starter-template-en-ai

Brings into this project the improvements its origin template received after instantiation — reads .template-origin, computes the tooling diff (skills, hooks, scripts, workflows) against the current template and offers to apply it. Use this when someone wants to update/sync the project with the template (e.g. "update the template", "pull in the template's new improvements").

2026-07-100

migration-guard

brayandiazc/project-starter-template-en-ai

Reviews a database migration before it ships to make sure it is safe — reversible, non-destructive, and backward-compatible — following the project's database conventions. Use this whenever you create, review, or approve a schema or data migration (e.g. "check this migration", "is this migration safe to deploy?").

2026-06-300

name	open-issue
description	Drafts and creates a GitHub issue by filling out the right template from .github/ISSUE_TEMPLATE/ based on the type (bug, feature, documentation, task, or question). Use this when the user asks to open/create an issue, report a bug, or record a task/request (e.g. "open an issue for this bug", "create an issue for the new feature", "log this task"). Does not close or comment on existing issues.
argument-hint	[title or short description]

Create a well-formed issue using the repository's template.

Look at the available templates in .github/ISSUE_TEMPLATE/ and pick the one that matches the issue type:
- bug_report.md — a defect or incorrect behavior.
- feature_request.md — a new feature or improvement.
- documentation_request.md — something missing or wrong in the docs.
- task.md — an internal work task (chore, refactor, tooling).
- support_question.md — a support question or doubt. If the type is ambiguous from $ARGUMENTS, ask before choosing.
Read the chosen template to learn its required sections and its front matter (title:, labels:, assignees:). Respect that front matter.
Fill in each section using the info from $ARGUMENTS and the conversation context:
- A clear, descriptive title (not generic like "bug").
- Reproduction steps / expected vs. actual behavior for bugs.
- Motivation and acceptance criteria for features and tasks.
- Leave as a prompt (don't invent) any data you don't have: versions, environment, screenshots.
Create the issue with the gh CLI following the template, e.g. gh issue create --title "…" --body "…" --label "…" (or --template <file> for the interactive flow). If there is no remote configured, output the filled issue for the person to paste into GitHub.
Report the URL of the created issue (or the drafted body).

Example: /open-issue login fails with Google on Safari → filled .github/ISSUE_TEMPLATE/bug_report.md, published.