Skip to content
cccskills
FreePublished on GitHub

report-issue

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.

The English summary is being prepared. Showing the original description.

PacificStudio/openase269 stars(GitHub 269 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Files included (2)

  • SKILL.md2.5 KB
  • scripts/create_issue_and_add_to_project.sh4.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

auto-harness

Free

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, structured logging, and technical-debt tracking. Use when Codex needs to audit drift-prone semantics that are repeated across code, docs, schemas, generated artifacts, frontend/backend boundaries, or CI, then design or implement guardrails with progressive disclosure and zero-tolerance contract checks.

The English summary is being prepared. Showing the original description.

PacificStudio/openase269Updated Aug 9, 2026

commit

Free

Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

The English summary is being prepared. Showing the original description.

PacificStudio/openase269Updated Aug 9, 2026

commit

Free

Write concise Conventional Commit messages that match the actual scope of the change.

The English summary is being prepared. Showing the original description.

PacificStudio/openase269Updated Aug 9, 2026

create-pr

Free

Prepare a crisp pull request summary with scope, validation, and rollout notes.

The English summary is being prepared. Showing the original description.

PacificStudio/openase269Updated Aug 9, 2026

deep-interview

Free

Clarify ambiguous requests with a focused, Socratic interview before planning or implementation.

The English summary is being prepared. Showing the original description.

PacificStudio/openase269Updated Aug 9, 2026

deploy-coolify-review-env

Free

Create or update a branch-scoped Coolify review environment with one command, and delete it with one command. Use when a ticket must deploy a preview before human review, while keeping the workflow simple and fast.

The English summary is being prepared. Showing the original description.

PacificStudio/openase269Updated Aug 9, 2026

See all skills by PacificStudio

Report a problem with this skill