Token导航 LogoToken导航TokenDH.com
中转站排行榜
研究检索需要联网github未标认证来源可访问clear审计通过

jql-query-builder（jql 查询生成器）

Agent Skill

jql-query-builder 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

16,641

周安装

518

GitHub Stars

2

下载量

7,395
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：jql-query-builder（jql 查询生成器）
来源仓库：https://github.com/sethdford/claude-plugins
仓库路径：skills/jql-query-builder
安装命令：
npx skills add https://github.com/sethdford/claude-plugins --skill 'JQL Query Builder'
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异；本站展示可直接复制的安装命令，安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/sethdford/claude-plugins --skill 'JQL Query Builder'

简介

帮助构建 Atlassian Jira Query Language (JQL) 语句。

  • 适用于筛选特定状态的 Issue 或生成报表视图。
  • 输出查询语句需经实际 Jira 环境验证有效性。
  • 避免使用可能返回海量数据的宽泛条件造成性能问题。
  • jql-query-builder 属于研究检索类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

JQL Query Builder

Expert assistance for constructing JQL (Jira Query Language) queries to search and filter Jira issues efficiently.

When to Use This Skill

  • User wants to search for specific issues
  • User needs to filter issues by multiple criteria
  • User mentions JQL or queries
  • User wants to find bugs, features, or tasks matching certain conditions
  • User needs help understanding JQL syntax

JQL Basics

Field Operators

OperatorDescriptionExample
=Equalsstatus = "In Progress"
!=Not equalspriority!= Low
>, <Greater/less thancreated > -7d
>=, <=Greater/less or equalpriority >= High
~Contains textsummary ~ "login"
INMatches any valuestatus IN (Open, "In Progress")
NOT INDoesn't matchpriority NOT IN (Low)
IS EMPTYField is emptyassignee IS EMPTY
IS NOT EMPTYField has valuedueDate IS NOT EMPTY

Common Fields

  • project: Project key (e.g., project = PROJ)
  • status: Issue status (e.g., status = "In Progress")
  • priority: Priority level (e.g., priority = High)
  • assignee: Assigned user (e.g., assignee = currentUser())
  • reporter: Who created it (e.g., reporter = currentUser())
  • created: Creation date (e.g., created >= -30d)
  • updated: Last update (e.g., updated > -7d)
  • type: Issue type (e.g., type = Bug)
  • labels: Labels (e.g., labels = urgent)
  • summary: Title text (e.g., summary ~ "authentication")
  • description: Description text (e.g., description ~ "error")

Date Functions

  • -1d, -7d, -30d: Relative dates (days ago)
  • -1w, -4w: Weeks ago
  • startOfDay(), endOfDay(): Day boundaries
  • startOfWeek(), endOfWeek(): Week boundaries

User Functions

  • currentUser(): The logged-in user
  • membersOf("group-name"): Users in a group

Logical Operators

  • AND: Both conditions must be true
  • OR: Either condition must be true
  • NOT: Negate a condition

Common Query Patterns

My Open Issues

assignee = currentUser() AND status != Done

Recently Updated Bugs

type = Bug AND updated >= -7d ORDER BY updated DESC

High Priority Unassigned Issues

priority = High AND assignee IS EMPTY AND status != Done

Issues Created This Sprint

project = PROJ AND created >= -14d AND type IN (Story, Task)

Overdue Issues

dueDate < now() AND status != Done ORDER BY dueDate ASC

Issues Mentioning Specific Feature

(summary ~ "authentication" OR description ~ "authentication") AND status != Done

Team's Work This Week

assignee IN membersOf("dev-team") AND updated >= startOfWeek()

Epics Without Stories

type = Epic AND issueFunction NOT IN linkedIssuesOf("type = Story")

Building Complex Queries

Step-by-Step Approach

  1. Start with project: project = PROJ
  2. Add status filter: project = PROJ AND status IN ("To Do", "In Progress")
  3. Add assignee: project = PROJ AND status IN ("To Do", "In Progress") AND assignee = currentUser()
  4. Add time filter: project = PROJ AND status IN ("To Do", "In Progress") AND assignee = currentUser() AND created >= -30d
  5. Add sorting: project = PROJ AND status IN ("To Do", "In Progress") AND assignee = currentUser() AND created >= -30d ORDER BY priority DESC, updated DESC

Optimization Tips

Use Specific Fields

❌ Slow: text ~ "bug" ✅ Fast: summary ~ "bug" OR description ~ "bug"

Limit Date Ranges

❌ Slow: created <= now() ✅ Fast: created >= -90d

Use IN Instead of Multiple OR

❌ Verbose: status = "To Do" OR status = "In Progress" OR status = "Review" ✅ Clean: status IN ("To Do", "In Progress", "Review")

Order Matters for AND

Put most restrictive conditions first:

assignee = currentUser() AND status != Done AND type = Bug

Testing Queries

When I build a query for you, I'll:

  1. Explain the logic: Break down what each part does
  2. Test it: Use /jira-search to verify results
  3. Refine: Adjust based on results
  4. Optimize: Suggest improvements for performance

Common Use Cases

Sprint Planning

project = PROJ AND status = "To Do" AND sprint IS EMPTY ORDER BY priority DESC

Bug Triage

type = Bug AND status = "To Do" AND priority IS EMPTY ORDER BY created DESC

Release Readiness

fixVersion = "v2.0" AND status != Done

Stale Issues

status = "In Progress" AND updated <= -30d

Blocked Work

status = Blocked OR labels = blocked ORDER BY priority DESC

Advanced Patterns

Find Issues Without Estimates

project = PROJ AND "Story Points" IS EMPTY AND type IN (Story, Task)

Parent Issues with Incomplete Subtasks

issueFunction IN parentsOf("status != Done")

Issues Mentioned in Comments

comment ~ "needs review"

Cross-Project Search

project IN (PROJ1, PROJ2, PROJ3) AND assignee = currentUser()

How I'll Help

When you need a JQL query, I will:

  1. Understand your requirements: What are you trying to find?
  2. Build the query: Construct JQL step-by-step
  3. Explain each part: Help you understand the syntax
  4. Test it: Run the query using /jira-search
  5. Refine: Adjust based on results
  6. Save for reuse: Document the query for future use

Example Interaction

You: "Find all high-priority bugs assigned to me that were updated in the last week"

Me: "I'll build a JQL query for that:

type = Bug AND priority = High AND assignee = currentUser() AND updated >= -7d ORDER BY updated DESC

Breaking it down:

  • type = Bug: Only bugs
  • priority = High: High priority only
  • assignee = currentUser(): Assigned to you
  • updated >= -7d: Updated in last 7 days
  • ORDER BY updated DESC: Newest first

Let me search for these issues using /jira-search..."

References

For more JQL details:

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

29.73%
按下载量换算2,199

windsurf

24.3%
按下载量换算1,797

trae

17.72%
按下载量换算1,310

OpenCode

11.67%
按下载量换算863

Codex

8.66%
按下载量换算640

Antigravity

3.16%
按下载量换算234

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API；具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源字段存在多来源差异，先按来源优先级自动处理，无法消解时进入异常复核队列。

来源信息

GitHub 仓库

github.com

/sethdford/claude-plugins

SKILL.md 来源

github.com

/sethdford/claude-plugins/tree/main/skills/jql-query-builder

skills-sh

skills.sh

/sethdford/claude-plugins/jql-query-builder

agentskills-to

agentskills.to

/sethdford/claude-plugins/jql-query-builder

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

jq-json-processing（JQ JSON processing 搜索）

jq-json-processing 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

jqopenclaw-node-invoker（jqopenclaw node invoker 搜索）

jqopenclaw-node-invoker 用于查找、检索和筛选相关信息，适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。