skills.rest
c2kaka
c2kakaCOMMUNITY
Explore all skills by this author →
𝕏@fanoykakaGitHub

jira-report-quality-issue

Create evidence-backed JIRA issues with screenshots after guarded preflight and explicit approval.

1|Updated May 15, 2026
Search Tags:#issue tracking#bug report#rest api#jira#approval workflow#quality review#screenshot evidence
One-click install
npx skills add https://github.com/c2kaka/fancy-skills --skill jira-report-quality-issue-c2kaka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-report-quality-issue
Source: https://github.com/c2kaka/fancy-skills/tree/main/skills/jira-report-quality-issue
Command: npx skills add https://github.com/c2kaka/fancy-skills --skill jira-report-quality-issue-c2kaka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Filing quality issues in JIRA after reviewing a coding delivery is error-prone: drafts lack evidence, duplicates get created, screenshots leak sensitive data, and failed writes leave the tracker in an unknown state. This Skill turns verified defects into well-formed JIRA issues only after a read-only preflight and explicit human approval. ## Core Features & Use Cases - Guarded two-phase workflow: A read-only preflight validates deployment type, identity, permissions, create metadata, attachment limits, and duplicate candidates before any write; apply runs only with an exact approved batch fingerprint. - Evidence-backed drafts with screenshot validation: Drafts follow a strict JSON schema, and PNG/JPEG/WebP screenshots are structurally validated, hashed (SHA-256), and visually reviewed before upload. - Duplicate and recovery handling: Semantic duplicate review with candidate digests, fingerprint-based recovery of uncertain creates, and a guarded attachment-only resume flow for partial outcomes. - Use Case: After reviewing a coding agent's delivery, you confirm two independent defects, attach sanitized screenshots, preview the full creation packet, approve it, and the Skill creates the issues assigned to your account and verifies every field via GET. ## Quick Start Ask the agent to review the current coding delivery and file JIRA issues for the confirmed defects using this skill, then approve the presented creation packet.

Frequently Asked Questions about jira-report-quality-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I file a JIRA bug from a code review automatically?▼

Review the delivery to confirm each defect's evidence and root cause, build a JSON draft per the schema, then run the preflight command. After approving the exact creation packet, run apply with the batch fingerprint to create and verify the issues.

How does the skill prevent duplicate JIRA issues?▼

Preflight searches unresolved issues in the target project and returns a candidate digest. You must semantically review candidates and record a decision of no-duplicate, use-existing, or create-despite-candidate before creation is allowed.

Does it support both JIRA Cloud and JIRA Server?▼

Yes. The client detects the deployment type via serverInfo and uses API version 3 with accountId for Cloud, or API version 2 with username for Server and Data Center, including the correct create metadata endpoints for each.

What screenshot formats can be attached to JIRA issues?▼

PNG, JPEG, and WebP files are supported. Each file is structurally validated, checked against the JIRA attachment size limit, hashed with SHA-256, and must pass a manual visual review for sensitive content before upload.

What happens if JIRA issue creation fails partway through?▼

The workflow stops on the first failure and records state such as partial, creation_outcome_unknown, or attachment_outcome_unknown. You can run a read-only verify command, and only a definitely missing attachment can be resumed through a separately approved resume flow.

Where does the skill read JIRA credentials from?▼

Credentials come only from the skill's own .env file containing JIRA_BASE_URL, JIRA_USER, JIRA_PASSWORD, JIRA_PROJECT_KEY, and JIRA_ISSUE_TYPE. The base URL must be a clean HTTPS origin, and credentials are never placed in command arguments or output.

Related Skills

Explore More Software Engineering Skills→
MinhmiceMinhmice

debugger

Investigate software defects and regressions using logs, traces, and diffs.

Community
Advanced
mindcockpit-aimindcockpit-ai
11

acceptance-verification

Verify GitHub issue acceptance criteria against codebase evidence.

Official
Advanced
elementalsoulselementalsouls
3.3k

evidence-hygiene

Enforces redaction and sanitization of sensitive data in bug-bounty evidence submissions.

Community
Intermediate
opsMachineopsMachine
1

implement-direct

Implement approved specs directly without test-driven development.

Official
Advanced