agentleFS
lgtm-hqlgtm-hq/ai-skills/skills/jira/SKILL.md

jira

Skill1 starsChanged 11 days agoMITView on GitHub

Generate Jira-style ticket descriptions. Use when the user says "/jira", "jira ticket", or "give me a Jira ticket".

63 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use confluence, meet and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SpillwaveSolutionsSkill

    confluence

    Manage Confluence documentation with downloads, uploads, conversions, and diagrams. Use when asked to "download Confluence pages", "upload to Confluence", "convert Wiki Markup", "sync markdown to Confluence", "create Confluence page", or "handle Confluence images".

    Also in 9 projects that use this

  • kv0906Skill

    meet

    Process meeting notes into structured notes with extracted decisions, blockers, and action items. Use for "/meet project type title" then paste notes.

    Also in 3 projects that use this

  • er1chuSkill

    monday

    Full Monday morning setup. Creates week folder, pulls carry-forward, and generates briefing in one pass. Use on Monday mornings or when the user says "monday", "start my week", or "monday morning".

    Also in 3 projects that use this

  • refly-aiSkill

    hubspot

    Integrate with HubSpot for CRM management. Use when you need to: (1) manage contacts and deals, (2) track sales pipelines, or (3) automate marketing and CRM workflows.

    Also in 4 projects that use this

  • koderoverSkill

    jenkins

    Jenkins CI/CD 操作。用于:(1) 触发 Jenkins 任务构建 (2) 查询任务状态和构建历史 (3) 获取构建日志 (4) 操作 Jenkins 节点和配置

    Also in 3 projects that use this

  • SentrySkill

    datadog

    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.

    Also in 3 projects that use this

The file

Files
SKILL.md

Jira Ticket

Generate a structured Jira ticket description from context (conversation, code changes, PR, or user description).

Output Format

**Title:** <imperative mood, concise>

**Type:** <Task | Bug | Story | Spike | Sub-task>

**Priority:** <Critical | High | Medium | Low>

**Component:** <infer from context, e.g. CI/CD, Auth, Tests, UI>

**Description:**

<1-2 sentences explaining the what and why>

**Acceptance Criteria:**
- <testable criterion>
- <testable criterion>
- ...

**PR:** <link if one exists>

Rules

  • Title: imperative mood, no Jira prefix (the user adds their own project key)
  • Description: concise — explain the problem and the solution direction, not implementation details
  • Acceptance criteria: specific, testable, checkboxable — not vague ("works correctly")
  • Priority: infer from context (security = High/Critical, cosmetic = Low, functional = Medium)
  • Component: infer from files touched or domain discussed
  • PR link: include if a PR was created in the same conversation
  • Omit optional fields (Epic, Sprint, Story Points) unless the user asks for them

Examples

Good acceptance criteria:

  • pr-auto-assign.yml assigns the PR author on opened events
  • bin/assign-random-codeowner.sh is deleted
  • CODEOWNERS review requests are unaffected

Bad acceptance criteria:

  • It works
  • The workflow is correct
  • Tests pass

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.