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_brief.md

View on GitHub
<!--
  BRIEF template = the shared header + table sections, ending at 'Trend Analysis'.
  The shared header/tables below are identical to report_template_detailed.md (lines 7-41).
  Keep them in sync; for the canonical full layout, see report_template_detailed.md.
-->
# 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}.

<!--
  Boundary marker: brief mode ends here. Do not append per-project
  blocks; for the detailed mode use report_template_detailed.md.
-->
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