jira-api

Provide Jira-context placeholder guidance for planning, QA, and PR workflows.

3|1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/zazzcode/zazz-skills --skill jira-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-api
Source: https://github.com/zazzcode/zazz-skills/tree/main/.agents/skills/jira-api
Command: npx skills add https://github.com/zazzcode/zazz-skills --skill jira-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira context is essential for planning, QA, and PR workflows in repos that rely on Jira, but live Jira connectivity is not yet implemented. This draft skill provides a placeholder and guidance to keep teams aligned and ready for integration.

Core Features & Use Cases

  • Placeholder guidance for Jira-backed workflows in planning, QA, and review processes.
  • Encourages using repo guidance (AGENTS.md) and user-provided Jira references to seed context.
  • Prepares downstream skills to consume authoritative Jira data once integration is available.

Quick Start

Provide a Jira issue key or URL to seed context for planning and QA activities.

Frequently Asked Questions about jira-api

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

FAQPage Schema
How do I provide Jira context for planning and QA workflows without a live API connection?

You can draft Jira context for planning and QA workflows by providing a Jira issue key or URL. This placeholder approach relies on repo guidance from AGENTS.md and user-provided references rather than fetching live data.

What is a Jira context placeholder and when do I need it for issue tracking?

A Jira context placeholder is a draft mechanism for issue tracking that seeds required Jira data into planning, requirement drafting, testing, and review scenarios when live Jira connectivity is not yet implemented in your repository.

Can I use this to fetch live Jira data for PR reviews and documentation?

No, it does not perform live API calls or data fetches. You must use user-supplied Jira references and repo guidance from AGENTS.md to prepare contexts for PR reviews and documentation.

Do I need AGENTS.md to set up Jira integration context for my repository?

Yes, you need AGENTS.md to set up Jira integration context. The skill requires repo guidance from AGENTS.md along with user-supplied Jira references to properly seed context for your workflows.

What are the limitations of using a placeholder approach for Jira issue tracking?

The limitation of this Jira issue tracking placeholder is that it cannot fetch live data or perform API calls. It only prepares downstream skills to consume authoritative Jira data once actual integration is available.