summarise-ecosystem-results

Use when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem results for a Ruff PR from a PR number, PR URL, GitHub ecosystem-results comment, or detailed HTML report.

Install
npx skills add 'https://github.com/astral-sh/ruff/tree/main/.agents/skills/summarise-ecosystem-results'
Download bundle ↓
main · 353969eScanned 2026-09-17

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗

assets/report-template.md

assets/report-template.mdBrowse 4 files
View on GitHub
← Back to SKILL.md

PR # ecosystem summary

<Summarize meaningful changes to project failures and diagnostic behavior, including changes involving intermittent severe failures, along with their significance. Lead with the analysis readers need; do not describe how the report was generated.>

Project failures

1. <New, fixed, or changed project failure>

Affected projects:

  • : merge base: <base outcome>; PR: <PR outcome>.

<Explain the crash, panic, overflow, timeout, or abnormal exit, including relevant stderr where applicable.>

Intermittent severe failures

1. <New or changed intermittent panic, crash, overflow, or timeout>

Affected projects:

  • : merge base: <base outcome and count/runs, or not present>; PR: <PR outcome and count/runs, or not present>.

Affected projects

1.

Report entries:

Existing ty issues: ty#

<minimal reproducer>

Reproduction

  • Detailed report: ecosystem-analyzer report
  • Actions run: run , attempt
  • Ruff comparison: <merge-base> to <pr-revision>
  • ecosystem-analyzer: <revision>
  • mypy-primer: <revision>
  • Dependency cutoff: <EXCLUDE_NEWER>
  • Project Python: <project: version, ...>
  • Project analysis mode: <project: strict or non-strict, ...>
  • Comparison method: <concise exact commands or method used to run both copied ty binaries, including --config analysis.strict-equality-semantics=true and --config analysis.strict-generic-narrowing=true for strict projects>
Referenced from SKILL.md