rank-changes

Rank GitHub commits, PRs, and issues by community interest into a JSON file.

35|9|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/Appsilon/mediforce --skill rank-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rank-changes
Source: https://github.com/Appsilon/mediforce/tree/main/apps/community-digest/plugins/community-digest/skills/rank-changes
Command: npx skills add https://github.com/Appsilon/mediforce --skill rank-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rank GitHub changes by community interest, helping maintainers surface the most engaging work.

Core Features & Use Cases

  • Rank changes such as commits, PRs, and issues by expected community interest.
  • Produce a structured ranking that includes fields like rank, score, category, title, description, source, sourceId, and url.
  • Use case: generate a digest for project maintainers and stakeholders.

Quick Start

Provide a list of recent repository changes to rank and run the skill to generate the output at /output/result.json.

Frequently Asked Questions about rank-changes

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

FAQPage Schema
How do I rank GitHub changes by community interest for my project?

To rank GitHub changes by community interest, provide a list of recent repository commits, PRs, and issues to generate a structured ranking that surfaces the most engaging work for maintainers.

What is a GitHub changes digest and how does it work?

A GitHub changes digest ranks commits, PRs, and issues by expected community interest using predefined scoring rules and categories, outputting a structured JSON file to help maintainers surface engaging work.

Can I rank GitHub issues and PRs across multiple repositories and timeframes?

Yes, you can rank GitHub issues and PRs across multiple repositories and timeframes. The ranking process evaluates recent changes and outputs a structured JSON file with a rankedChanges array.

What format does the GitHub changes ranking output use?

The GitHub changes ranking output uses a JSON file format located at /output/result.json. It contains a rankedChanges array with fields like rank, score, category, title, source, and url, plus a metadata object.

Does ranking GitHub commits by community interest require any external dependencies?

Ranking GitHub commits by community interest requires no external dependencies. You simply provide the list of recent repository changes, and the skill applies its internal scoring rules to generate the ranking.

What limitations exist when generating a maintenance digest for GitHub changes?

When generating a maintenance digest for GitHub changes, the output is strictly a structured JSON file at /output/result.json. The ranking relies on predefined scoring rules and categories defined internally within the skill.