skills.rest
al-stev
al-stevCOMMUNITY
Explore all skills by this author →
GitHub

jira-check

Identify stale WB- Jira issues and prepare FE-UPDATE drafts with source citations.

1|Updated Apr 7, 2026
Search Tags:#slack#jira#atlassian#triage#issue-tracking#customer-support#fe-update
One-click install
npx skills add https://github.com/al-stev/field-eng-skills --skill jira-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-check
Source: https://github.com/al-stev/field-eng-skills/tree/main/.claude/skills/jira-check
Command: npx skills add https://github.com/al-stev/field-eng-skills --skill jira-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the manual work of finding stale customer Jira issues, gathering relevant Slack context, and keeping FE-UPDATE comments accurate and timely so SEs can communicate status without hunting across tools.

Core Features & Use Cases

  • Cross-customer sweeps and targeted triage: run an all-customer scan or focus on a single customer or WB- key to find stale or missing FE-UPDATEs.
  • Comprehensive briefings: aggregate full Jira histories and Slack threads, convert channel IDs to readable names, synthesize timelines, and surface FE-UPDATE histories.
  • Draft-and-approve workflow with safety: generate FE-UPDATE drafts with explicit source citations, show exact text to the SE, and require explicit approval before posting any comments.

Quick Start

Ask the assistant to run /jira-check GResearch to triage that customer's WB- issues, gather Slack context, and prepare FE-UPDATE drafts for review.

Frequently Asked Questions about jira-check

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

FAQPage Schema
How do I find stale customer Jira issues and draft FE-UPDATE comments?▼

To find stale customer Jira issues and draft FE-UPDATE comments, you can run cross-customer sweeps or per-customer triage on WB- project keys to identify outdated tickets and generate update drafts for review.

Can I aggregate Slack threads to gather context for Jira issue triage?▼

Yes, you can aggregate Slack threads to gather context for Jira issue triage. The process fetches full Slack thread histories and converts channel IDs into readable names to synthesize comprehensive briefings.

How does the draft-and-approve workflow work for posting FE-UPDATE comments on Jira issues?▼

The draft-and-approve workflow for posting FE-UPDATE comments generates drafts with explicit source citations, displays the exact text to the software engineer, and requires explicit approval before posting any comments to the Jira issue.

Do I need to validate specific WB- keys before looking up Jira issue histories?▼

Yes, you need to validate specific WB- keys before looking up Jira issue histories. The system validates the WB- keys, fetches full Jira histories, and synthesizes timelines with source citations for accurate issue tracking.

What is the best way to maintain FE-UPDATEs across all customers in Jira?▼

The best way to maintain FE-UPDATEs across all customers in Jira is running an all-customer sweep to scan for stale or missing FE-UPDATE comments and prepare drafted updates for explicit SE approval.

Related Skills

Explore More Software Engineering Skills→
louderthanthunderx1louderthanthunderx1

management-talk

Rewrite engineering updates for leadership audiences across JIRA, Slack, and email.

Community
Intermediate
al-steval-stev

3p-update

Synthesize Asana tasks, Jira issues, and Slack messages into Progress/Plans/Problems updates.

Community
Advanced
opendatahub-ioopendatahub-io
36

vLLM Slack Summary

Export vLLM CI Slack messages and convert them into markdown transcripts.

Official
Intermediate
lwndevlwndev
2

managing-work-items

Automate GitHub and Jira issue tracking with fetch, comments, and PR links.

Community
Advanced