New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Report Issue

by PacificStudio in PacificStudio/openase

Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo).

Apache-2.0Auto-check: notesDevOps & Cloud

Install Report Issue

skills CLI
$ npx skills add PacificStudio/openase --skill report-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PacificStudio/openase report-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PacificStudio/openase.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/report-issue .claude/skills/report-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
report-issue
GitHub stars
268
Token cost
~631 tokens
SKILL.md length
293 words
Files
2 (incl. scripts)
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo).

  • Works in 5 steps: Gather concrete facts from the running… → Draft the issue body in a temp Markdown… → Create the issue with the helper script.… → …
  • Asked to report a bug
  • SKILL.md covers Goals, Inputs To Collect, Body Structure and Workflow, plus 1 more section
  • Runs Shell scripts from its folder; calls git

What it does

Report Issue is an agent skill from PacificStudio/openase. Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo). Use when asked to report a bug, deployment regression, local repro, or design task into GitHub with reproducible evidence and project binding.

Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/create_issue_and_add_to_project.sh`).

It sits in DevOps & Cloud, covering Deployment. It works with GitHub. The repository describes itself as: Ticket-Driven Automated Software Engineering. OpenASE is an all-in-one platform that turns tickets into working code — AI agents automatically pick up tickets, execute workflows… The licence is Apache-2.0.

When your agent uses it

  • Asked to report a bug
  • Deployment regression
  • Design task into GitHub with reproducible evidence and project binding

Example prompts

  • “/report-issue”

Requirements

  • A Bash shell
  • Docker

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Gather concrete facts from the running repo and local deployment.
  2. Draft the issue body in a temp Markdown file.
  3. Create the issue with the helper script. The helper must run in this order
  4. Run
  5. Return the issue URL and confirm the actual project status that was set.

What it can do on your machine

Read from SKILL.md and the folder at commit e530faf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Report Issue loads about 631 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 293 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~631

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:28
    - whether `.env` was sourced

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from PacificStudio/openase at commit e530faf, republished under its Apache-2.0 licence (© PacificStudio). 293 words, ~631 tokens.

Download SKILL.mdSave it as .claude/skills/report-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
report-issue
description
Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo). Use when asked to report a bug, deployment regression, local repro, or design task into GitHub with reproducible evidence and project binding.

Report Issue

Goals

  • Create a high-signal GitHub issue in the current repo.
  • Optionally wire blocked by dependencies before project binding.
  • Add it to project OpenASE Automation (#2) with the requested status.
  • Default to Todo when the caller does not specify a status.
  • Keep issue bodies concrete: exact branch, commit, commands, actual result, expected result, impact, and likely fix direction.

Inputs To Collect

  • Current branch: git branch --show-current
  • Current commit: git rev-parse HEAD
  • Relevant environment facts:
    • deployment mode
    • local ports
    • whether .env was sourced
    • whether Docker/PostgreSQL was involved
  • Exact repro command or API sequence
  • Exact error text or log excerpt

Body Structure

Write issue bodies with these sections when applicable:

  • Summary
  • Environment
  • Reproduction
  • Actual Result
  • Expected Result
  • Likely Cause
  • Impact
  • Suggested Fix Direction

Prefer exact commands and exact errors over paraphrase.

Workflow

  1. Gather concrete facts from the running repo and local deployment.
  2. Draft the issue body in a temp Markdown file.
  3. Create the issue with the helper script. The helper must run in this order:
    • create issue
    • add blocked by dependencies, if any
    • add to project
    • set project status
  4. Run:
    • .codex/skills/report-issue/scripts/create_issue_and_add_to_project.sh --title "<title>" --body-file <file> [--status "<status>"] [--blocked-by <issue-number> ...]
  5. Return the issue URL and confirm the actual project status that was set.

Supported --status values:

  • Backlog
  • Todo
  • In Progress
  • Rework
  • In Review
  • Merging
  • Done
  • Canceled
  • Duplicated

Notes

  • Use one issue per distinct failure mode.
  • Do not merge unrelated regressions into one issue.
  • When a request includes multiple related tasks, create the parent and blocker issues first so later issues can reference them via --blocked-by.
  • If the issue is a design task, explicitly state the desired contract and acceptance criteria.
  • If the issue references PRD drift, say that PRD must be updated to remain the latest semantic source of truth.

© PacificStudio, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in .codex/skills/report-issue of PacificStudio/openase.

  • SKILL.md
  • scripts/create_issue_and_add_to_project.sh

Open the folder on GitHubat commit e530faf

Compare with similar skills

Report Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Report Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Report Issue this skillPacificStudio/openase268—~631Automated safety check: NotesApache-2.0
AI News RadarLearnPrompt/ai-news-radar1.8k—~2.5kAutomated safety check: NotesMIT
Reflexo ReleaseMyriad-Dreamin/typst.ts1.2k—~1.5kAutomated safety check: PassApache-2.0
Use Vercel Actionamondnet/vercel-action765—~2.7kAutomated safety check: PassMIT
1panel App Builderarch3rPro/1Panel-Appstore213—~1.3kAutomated safety check: PassMIT
Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template786—~5.9kAutomated safety check: NotesMIT

Similar skills

  • AI News Radar

    LearnPrompt/ai-news-radar

    A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…

    1.8k GitHub stars~2.5k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Reflexo Release

    Myriad-Dreamin/typst.ts

    Guide Reflexo/typst.ts release preparation and operator handoffs.

    1.2k GitHub stars~1.5k tokensUpdated 13 days ago
    DevOps & CloudAuto-check passed

  • Use Vercel Action

    amondnet/vercel-action

    Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.

    765 GitHub stars~2.7k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • 1panel App Builder

    arch3rPro/1Panel-Appstore

    A skill your agent uses when packaging Docker deployments as 1Panel local app store apps, including GitHub projects, docker-compose.yml files, docker run commands, app metadata, version directories…

    213 GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Prepare Cloudflare Production Deployment

    LubomirGeorgiev/cloudflare-workers-nextjs-saas-template

    Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.

    786 GitHub stars~5.9k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Broccoli Oss GCP Deploy

    besimple-oss/broccoli

    Deploy this repository to a new Google Cloud project using the repo's existing Cloud Run, Cloud Run Jobs, Cloud SQL, Secret Manager, and Artifact Registry scripts.

    286 GitHub stars~4.1k tokensUpdated 5 mo ago
    DevOps & CloudAuto-check passed

More from PacificStudio/openase

All 14 skills in this repo

  • Deploy Coolify Review Env

    PacificStudio/openase

    Create or update a branch-scoped Coolify review environment with one command, and delete it with one command.

    268 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check: notes

  • Deploy Openase

    PacificStudio/openase

    Build and locally redeploy OpenASE from the current branch, including web static assets and the Go binary, then restart the local service and verify health.

    268 GitHub stars~564 tokensUpdated 1 mo ago
    Auto-check: notes

  • Local Bootstrap CLI Auth Debug

    PacificStudio/openase

    Diagnose and repair OpenASE CLI access in local bootstrap mode.

    268 GitHub stars~778 tokensUpdated 1 mo ago
    Auto-check passed

  • Push

    PacificStudio/openase

    Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.

    268 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Auto Harness

    PacificStudio/openase

    Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding…

    268 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Openase Platform

    PacificStudio/openase

    Platform operations for tickets, projects, and runtime coordination inside OpenASE.

    268 GitHub stars~6.4k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Report Issue

What does Report Issue do?

Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo). Report Issue is an agent skill from PacificStudio/openase. Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo).

When should I use Report Issue?

Report Issue fits situations like: asked to report a bug; deployment regression; design task into GitHub with reproducible evidence and project binding.

How do I install Report Issue in Claude Code?

Run `npx skills add PacificStudio/openase --skill report-issue -a claude-code`. Or copy the skill folder (.codex/skills/report-issue in PacificStudio/openase) into .claude/skills/report-issue in your project. Claude Code loads it when a task matches its description.

How do I install Report Issue in Codex?

Run `npx skills add PacificStudio/openase --skill report-issue -a codex`. Or copy the skill folder (.codex/skills/report-issue in PacificStudio/openase) into .agents/skills/report-issue in your project. Codex loads it when a task matches its description.

Can I use Report Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PacificStudio/openase --skill report-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/report-issue, .gemini/skills/report-issue, .github/skills/report-issue and .opencode/skills/report-issue in your project.

What does Report Issue need to run?

Going by SKILL.md and its folder, Report Issue needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell; Docker.

Does Report Issue access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Report Issue safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Report Issue use?

Report Issue is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Report Issue use?

About 631 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Report Issue?

Skills that share tags, products or a category with Report Issue: AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars), Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars), Use Vercel Action (amondnet/vercel-action, 765 stars) and 1panel App Builder (arch3rPro/1Panel-Appstore, 213 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Report Issue?

PacificStudio (a GitHub organization) maintains it in PacificStudio/openase, which has 268 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on August 9, 2026.

Source: PacificStudio/openase on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.