Stars and mentions
Last 30 days, Oct 5 – Nov 3
Package downloads
Cumulative recorded downloads · since 2025-10-31
Across 1 known packages in repositories tcorral owns. Cumulative totals include recorded downloads before the selected range. Missing observations leave gaps; totals may be incomplete.
Top repositories
tcorral’s repositories ranked by pull request authors, as on trending.
Contributes to
Repositories outside tcorral’s account where tcorral opened or reviewed pull requests in the past 365 days.
Who noticed tcorral
Everyone who starred or forked tcorral’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
- Gold
- 01st place finishes
- Silver
- 12nd place finishes
- Bronze
- 23rd place finishes
- Awarded repositories
- 2Owned by tcorral now
Repositories
Ordered by gold, then silver, then bronze.
- Design-Patterns-in-JavascriptBest: 2nd by stars, 105 stars011
- Cutter.jsBest: 3rd by stars, 25 stars001
Every award
Top-three finishes of these repositories in completed trending days and weeks, newest first.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
I built a Claude Code skill that generates documentation and Mermaid diagrams for GitHub Actions Hey everyone! I've been working on a Claude Code skill to make GitHub Actions workflows easier to understand and document. As repositories grow, figuring out how workflows, reusable workflows, and composite actions connect can become a bit of a headache. And keeping that documentation up to date is another story. So I built github-actions-docs. It scans your .github directory and generates: - Markdown documentation for each workflow and local action - Mermaid dependency graphs showing how everything connects - Sequence diagrams explaining workflow execution - Details about triggers, jobs, secrets, permissions, and configuration - Warnings about things like broken references and unpinned actions Under the hood, it combines deterministic Python scripts for scanning and validation with Claude for writing the explanations and diagrams. You can also regenerate the docs without losing notes you've added manually. The skill only reads your .github directory and doesn't modify your workflows. GitHub: tcorral/github-actions-docs It's open source (MIT license). I'd love to hear what you think, especially if you work with complex GitHub Actions setups. Feedback and contributions are welcome!