Skip to content

Dianel555/DSkills / skills/github-trending-analyzer

github-trending-analyzer

Verified

Crawl GitHub trending repositories, analyze with LLM for Chinese insights, categorize by themes, compute diffs against history, and generate Markdown reports. Default brief mode stops at trend analysis; optional detailed mode appends per-project analysis. Supports incremental gap-filling and selective re-analysis with caching.

FileKindSize
SKILL.mdskill md11.1 KB
report_template_brief.mdmarkdown1.4 KB
report_template_detailed.mdmarkdown1.7 KB
theme_rules.jsonconfig2.1 KB

report_template_detailed.md

View on GitHub
<!--
  Detailed report = the full brief report (report_template_brief.md,
  through "Trend Analysis") FOLLOWED BY the per-project blocks below.
  Do NOT emit the detailed blocks without the brief header above them.
-->

# GitHub Trending Report - {date}

> Generated: {date}
> Source: github.com/trending?since={since}
> Baseline: {baseline_date}

## 🔥 New Entries

| Rank | Project | Language | ⭐ Stars | 📈 Today | One-liner |
|------|---------|----------|---------|---------|-----------|
| 1 | [org/repo](url) | Python | 12.3k | +500 | What it does |

## ⭐ Sustained Hot

| Project | Language | ⭐ Stars | 📈 Today | Why notable |
|---------|----------|---------|---------|-------------|
| [org/repo](url) | Go | 8.5k | +300 | What makes it special |

## 📉 Dropped Off

| Project | What it might mean |
|---------|-------------------|
| org/repo | Hype cycle cooling |

## 🎯 Theme Breakdown

**🤖 AI/LLM** (5 projects): org/repo1(+600), org/repo2(+450), ...

**🛠️ Dev Tools** (3 projects): org/tool1(+200), org/tool2(+150), ...

## 💡 Trend Analysis

{trend_insight_paragraph}

Current wave: {dominant_theme} projects surge due to {driver}. Notable shift from {previous_trend}.

---

## 📋 Project Details

### {Project Name}

**Stars**: {total_stars} (+{today_increment})
**Language**: {primary_language}
**URL**: {github_url}

#### 这是什么
{what_description}

#### 生活化类比
{analogy_sentence}

#### 它能帮你做什么
1. {help_point_1}
2. {help_point_2}
3. {help_point_3}

#### 谁需要它
{who_description}

---

<!-- Repeat the block above for each project. In deep mode, help may
     carry 3 items; otherwise use the first 2. Field labels stay Chinese
     to match the SKILL.md 4-field analysis schema (what/analogy/help/who). -->
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall