/github-issue

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select github-issue from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv github-issue, /just-vibe github-issue and /jv:github-issue in Claude. See shortcut setup and context examples.

What the agent does

1. Inspect repository templates and related issues to avoid a duplicate.
2. Write only verified facts: separate expected from actual behavior and include a minimal reproduction or acceptance criteria, the tested version and sanitized logs.
3. All changes are owned by the user. Add no agent/model self-attribution, AI-generated signature, badge, or agent Co-authored-by trailer to commits, PRs, comments, release notes or messages. Use the existing user Git identity; preserve legitimate human attribution and required third-party notices.

Inputs

• bug/feature report, target repository, reproduction, and expected outcome.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Actionable issue draft; submit only when explicitly instructed to create/post it.

Writes

Inspect/plan: draft from available evidence without posting. Apply: create or update only the issue the user requested in the resolved repository; preserve prior submission identity and do not post duplicates after uncertain responses.

Mode

Plan or draft an issue locally; apply for explicitly requested creation or updates in a resolved repository. Reconcile uncertain submissions before retrying.

Prerequisites

Exact owner/repository and relevant issue/PR/ref; authenticated read access through an available connector or CLI for remote evidence. External writes require the requested operation, appropriate account permissions, and rechecking target state. Local preparation remains useful without write access.

Expected output

• Reviewable title, body and metadata with the target repository and duplicate check, and the created issue URL only when creation was observed.

How the work is checked

• Unknown reproduction details remain questions; a submitted issue uses the specified repository and avoids accidental duplicates.
• Review newly prepared commit/PR/message text, including template or hook additions, for agent self-attribution before submission; verify the resulting artifact when available. Do not silently rewrite existing history or remove human credits.

When to stop or clarify

• Do not invent severity or affected versions. After uncertain submission, search for the created issue before retrying.

Handling missing context

Infer

Resolve owner/repository and PR/issue/ref from links, remotes and supplied artifacts; inspect available account and head identity.

Assume

Prepare local text or analyze supplied evidence if remote access is absent; label its freshness.

Ask

Ask only when repository/account/target ambiguity blocks the requested remote action; missing write access does not block local drafting.

Technical guidance

Evidence

Collect expected/actual behavior, minimal trigger, version, environment and redacted evidence.

Method

Separate confirmed reproduction from hypothesis and define an observable acceptance condition.

Pitfall

Pasting raw logs can expose tokens; an unverified root-cause claim can misdirect the eventual repair.

Check

Ensure another developer can attempt the reproduction from the draft without private state or invented evidence.

Situational decisions

When creation returns an uncertain result: Search for the attempted issue using repository and distinctive content before retrying.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring