skills.rest
forcedotcom
forcedotcomOFFICIAL
Explore all skills by this author →
Website𝕏@salesforcedevsGitHub

shipped-issues

Identifies and closes GitHub issues whose linked GUS work items shipped in the CHANGELOG.

1.0k|454|Updated Jun 21, 2017
Search Tags:#issue triage#SOQL#gus#gitHub issues#ChangeLog#Salesforce CLI#release cleanup
One-click install
npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill shipped-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipped-issues
Source: https://github.com/forcedotcom/salesforcedx-vscode/tree/main/.claude/skills/shipped-issues
Command: npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill shipped-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open GitHub issues often remain open even after the underlying work item was completed and shipped in a release, leaving the issue tracker cluttered and misleading. This Skill cross-references open issues against GUS work item statuses and the shipped CHANGELOG to find issues that were fixed but never closed.

Core Features & Use Cases

  • Cross-Reference Detection: Extracts W- work item references from open GitHub issues and queries GUS via SOQL to verify each work item is in a closed terminal status.
  • CHANGELOG Verification: Confirms each candidate issue number actually appears in the shipped CHANGELOG on the develop branch before flagging it as shipped.
  • Review-Before-Close Workflow: Presents a report table of shipped issues and near-misses, then closes issues with an explanatory comment only after explicit user confirmation.
  • Use Case: After a release of the Salesforce Extensions for VS Code, run this Skill to find all open issues whose fixes shipped in that release and close them with a comment citing the CHANGELOG entry.

Quick Start

Ask the assistant to run the shipped-issues cleanup to find and close GitHub issues whose fixes have already shipped.

Frequently Asked Questions about shipped-issues

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

FAQPage Schema
How do I close GitHub issues that were fixed in a release?▼

List open issues containing W- work item references, query GUS via SOQL to confirm each work item is closed, then verify the issue number appears in the shipped CHANGELOG. Close confirmed issues with gh issue close and a comment citing the CHANGELOG entry.

How do I query GUS work item status with the Salesforce CLI?▼

Run sf data query with a SOQL statement selecting Name, Status__c, and closed date from ADM_Work__c, targeting the GUS org alias with -o gus. Batch work item names in chunks of about 50 to stay within SOQL limits.

Does this close issues automatically without review?▼

No. The workflow presents a report table of shipped candidates and near-misses first, and only closes issues after explicit user confirmation. Each closure includes a comment referencing the CHANGELOG line and the closed work item.

What happens when an issue has multiple work items with mixed statuses?▼

The issue is skipped until every linked W- work item reaches a closed terminal status. If any work item is still open, the issue is excluded from closure and can appear in the near-miss list for review.

Why is an issue not closed even though its work item is closed?▼

Closure also requires the issue number to appear in the CHANGELOG as ISSUE #N or an issues/N link. Closed work items without a CHANGELOG match are listed as near-misses, since the fix may be under-the-hood and not customer-facing.

Related Skills

Explore More Software Engineering Skills→
forcedotcomforcedotcom
1.0k

gus-cli

Query, create, and update Gus work items and epics via sf CLI.

Official
Intermediate
monomono
5.6k

release-milestones

Reconcile shipped pull requests and maintain Chromium-derived release milestone dates.

Official
Intermediate
mastra-aimastra-ai
27.6k

factory-complete-issue

Marks a GitHub issue as done and updates its status labels via gh CLI.

Official
Basic
kingheu0818-sketchkingheu0818-sketch

source-command-dedupe

Find likely duplicate GitHub issues and post a structured comment.

Community
Intermediate