peach-check

Analyze and classify Peach Main Analysis failures for SonarJS releases.

1.3k|191|Updated May 15, 2012
One-click install
npx skills add https://github.com/SonarSource/SonarJS --skill peach-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: peach-check
Source: https://github.com/SonarSource/SonarJS/tree/main/.claude/skills/peach-check
Command: npx skills add https://github.com/SonarSource/SonarJS --skill peach-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, mc, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you triage Peach Main Analysis failures and decide if Peach blocks a SonarJS release. It provides a summary focused on SonarJS ownership and classifies findings with a guide.

Core Features & Use Cases

  • Peach Run Analysis: Check the latest Peach run and analyze failed jobs.
  • Analysis-Consistency Check: Verify if the current Peach state is consistent with recent history.
  • Classification Guide: Classify findings using a provided guide.
  • Summary & Release Recommendation: Provide a summary of the analysis and a release recommendation based on the findings.
  • Use Case: Before releasing SonarJS, use this Skill to ensure that any issues identified by Peach are addressed and consistent with recent history.

Quick Start

Use the peach-check skill with a specific run ID, like '/peach-check 12345', to analyze that run.

Frequently Asked Questions about peach-check

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

FAQPage Schema
How do I triage Peach Main Analysis failures for a SonarJS release?

You can triage Peach Main Analysis failures by analyzing failed jobs, verifying consistency with recent history, and classifying findings to determine if they block a SonarJS release.

What is analysis consistency check in Peach release triage?

Analysis consistency check verifies if the current Peach state matches recent history, helping distinguish persistent issues from new failures during SonarJS release triage.

Do I need gh and mc tools to analyze Peach job failures?

Yes, the gh and mc command-line tools are required dependencies for fetching GitHub job data and accessing the Peach API to perform historical analysis checks.

How do I check the latest Peach run for SonarJS analysis failures?

Invoke the Skill with a specific run ID to analyze the latest Peach run, check failed jobs, and receive a summary with a release recommendation based on SonarJS ownership.

Can I classify Peach Main Analysis findings using a provided guide?

Yes, the Skill provides a classification guide to categorize findings from the Peach Main Analysis, ensuring consistent triage and accurate release recommendations for SonarJS.

What are the limitations of using Peach API for SonarJS release triage?

The primary limitation is its dependency on external APIs; without access to GitHub and Peach APIs via gh and mc tools, the Skill cannot fetch job data or verify historical analysis consistency.