update-stars

Refresh displayed GitHub star counts across Remotion homepage components and push to main.

57.9k|4.4k|Updated Jun 23, 2020
One-click install
npx skills add https://github.com/remotion-dev/remotion --skill update-stars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-stars
Source: https://github.com/remotion-dev/remotion/tree/main/.agents/skills/update-stars
Command: npx skills add https://github.com/remotion-dev/remotion --skill update-stars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Remotion homepage displays GitHub star counts in multiple components, and these numbers become stale as the repository grows. This Skill automates fetching the current count and updating every display location so visitors always see accurate social proof.

Core Features & Use Cases

  • GitHub Star Lookup: Queries the current star count for the Remotion repository.
  • Rounded Display Update: Rounds the count down to the nearest 1000 and writes it to three specific component files.
  • Automated Commit & Push: Commits the updated values and pushes the change directly to the main branch.
  • Use Case: A maintainer wants the homepage to reflect the latest star count without manually editing three separate TypeScript files and running git commands.

Quick Start

Use the update-stars skill to refresh the GitHub star count on the Remotion homepage and push the change to main.

Frequently Asked Questions about update-stars

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

FAQPage Schema
How do I update the GitHub star count on a project homepage?

Fetch the current star count from the GitHub API, round it down to the nearest 1000, and update the values in each component file that displays the number. Then commit and push the changes to the main branch.

What files display the GitHub star count on the Remotion homepage?

The star count appears in CommunityStatsItems.tsx, GitHubButton.tsx, and TrustSection.tsx within the packages/promo-pages/src/components directory. All three must be updated to keep the homepage consistent.

Should star counts be rounded up or down when displayed?

Always round down to the nearest 1000. Rounding up would overstate the actual count and mislead visitors about the project's traction.

Why are star counts rounded to the nearest 1000?

Rounding prevents the displayed number from changing with every new star and keeps the UI clean. Rounding down specifically avoids overstating the project's popularity.

Can this skill update other repository metrics besides stars?

No, this skill is scoped specifically to GitHub star counts across three predefined component files. Other metrics like forks or watchers require separate handling.