issue-creation

Enforces GitHub issue templates, statuses, and approval workflow for Agent Teams Lite.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill issue-creation-jnzader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/JNZader/javi-ai/tree/main/upstream/agent-teams-lite/skills/issue-creation
Command: npx skills add https://github.com/JNZader/javi-ai --skill issue-creation-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Issue creation workflows are often ad-hoc, leading to inconsistent labeling, missing templates, and manual triage delays. This skill enforces a standardized process for creating issues and coordinating maintainer approvals, improving collaboration and PR readiness.

Core Features & Use Cases

  • Enforces mandatory issue templates (Bug Report / Feature Request) to ensure required fields and structure
  • Automatically marks new issues with status:needs-review to trigger triage and alignment
  • Requires maintainer approval (status:approved) before a PR can be opened
  • Directs conversations to Discussions for questions, reducing clutter in issues

Quick Start

Create an issue using the Bug Report or Feature Request templates to ensure proper labeling and approval workflow.

Frequently Asked Questions about issue-creation

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

FAQPage Schema
How do I enforce mandatory issue templates for GitHub bug reports and feature requests?

To enforce mandatory GitHub issue templates, this skill applies standardized Bug Report and Feature Request structures to ensure required fields are populated during issue creation. This prevents ad-hoc reporting and improves triage alignment across the project.

Can I require maintainer approval before a pull request is opened on GitHub?

Yes, you can require maintainer approval before a pull request by using this skill to gate PRs. It enforces a rule that a maintainer must add the status:approved label to an issue before any associated PR can be opened.

How does automatic triage work for newly created GitHub issues?

Automatic triage for new GitHub issues works by applying the status:needs-review label immediately upon issue creation. This status tag triggers maintainer review and alignment before any development work or PR approval begins.

What is the best way to keep GitHub issues clean from support questions and discussions?

The best way to keep GitHub issues clean from support questions is to direct those conversations to GitHub Discussions. This skill includes workflow logic that reduces clutter by routing questions away from the issue tracker.

Does this GitHub issue workflow skill work with Agent Teams Lite?

Yes, this GitHub issue workflow skill works with Agent Teams Lite. It automates and enforces standardized issue creation, triage, and PR approval gating specifically within the Agent Teams Lite environment.