Github Stars Playbook

Get GitHub Stars Fast — 14-Day Growth Sprint

🌍 Language / 语言: 中文 | English | 日本語 | 한국어

📦 Install

clawhub install github-stars-playbook

What you get after installing:

• Month-over-month 300+ star growth system (content rhythm + community ops)
• Contributor & Ambassador recruitment framework
• Event-driven growth playbook (Hacktoberfest, launches, milestones)

---

Stop waiting for organic discovery. This is the 14-day blitz to hit GitHub Trending.

• Day-by-day plan: Exactly what to post, where, and when
• Show HN strategy: Title formulas and timing that reach the front page
• Reddit playbook: Which subreddits, what format, how to avoid bans
• Star velocity science: The threshold math behind GitHub Trending
• Compounding: How to maintain momentum after the sprint

Related Gingiris Skills

• Full version: https://clawhub.ai/skill/gingiris-opensource
• All skills: https://clawhub.ai/user/gingiris
• Follow: @WeiYipei on X

Get GitHub Stars Fast — 14-Day Growth Sprint

Stop waiting for organic discovery. This is the 14-day blitz to hit GitHub Trending. Based on growing AFFiNE from 0 to 60k+ stars and consulting for 50+ OSS projects.

The 14-Day Plan

Phase 1: Foundation (Days 1-3)

Phase 2: Ignition (Days 4-7)

Phase 3: Amplification (Days 8-11)

Phase 4: Sustain (Days 12-14)

Show HN Strategy

Title Formulas That Work

• "Show HN: [Product] – [One benefit in ≤8 words]"
• "Show HN: I built [X] because [relatable frustration]"
• "Show HN: [X] — open-source alternative to [known product]"

Timing

• Best: Tuesday–Thursday, 10 AM EST
• Avoid: Weekends, Monday mornings, Friday afternoons
• Resubmit once if first attempt gets <5 points in 1 hour

Reddit Playbook

Best Subreddits for OSS

Anti-Ban Rules

• No direct "please star my repo" asks
• Lead with value, link at the end
• Don't post to multiple subs within 1 hour
• Engage in comments genuinely

Star Velocity Science

• GitHub Trending (daily): ~50-100 stars/day
• GitHub Trending (weekly): ~200 stars over 3 days
• The algorithm weighs recent velocity over total count
• A burst of 100 stars in 6 hours > 100 stars in 7 days

Post-Sprint Compounding

• Set up weekly content cadence (1 post/week minimum)
• Create "good first issue" pipeline for contributors
• Run monthly community events (hackathons, AMAs)
• Track star velocity weekly and optimize channels

Built by Gingiris — follow @WeiYipei on X for developer marketing tips.

GitHub スターを急速に獲得 — 14日間グローススプリント

オーガニック発見を待つのはやめましょう。これは GitHub Trending 入りを狙う14日間の集中施策です。AFFiNE を0から60k+スターに成長させ、50以上の OSS プロジェクトをコンサルした経験に基づきます。

14日間プラン

Phase 1: 基盤構築（Days 1-3）

Phase 2: 点火（Days 4-7）

Phase 3: 増幅（Days 8-11）

Phase 4: 維持（Days 12-14）

Show HN 戦略

効果的なタイトルフォーミュラ

• "Show HN: [プロダクト] – [8語以内のベネフィット]"
• "Show HN: [X]を作りました。[共感できる不満]だったので"
• "Show HN: [X] — [有名プロダクト]のオープンソース代替"

タイミング

• ベスト: 火〜木曜、EST 10AM
• 避ける: 週末、月曜朝、金曜午後
• 1時間で5ポイント未満なら1回だけ再投稿

Reddit プレイブック

OSS に最適なサブレディット

BAN 回避ルール

• 直接的な「スターください」は NG
• 価値をリードに、リンクは最後に
• 1時間以内に複数サブに投稿しない
• コメントには誠実にエンゲージ

スターベロシティの科学

• GitHub Trending（デイリー）: 約50-100スター/日
• GitHub Trending（ウィークリー）: 3日で約200スター
• アルゴリズムは合計数より直近のベロシティを重視
• 6時間で100スター > 7日で100スター

スプリント後の複利成長

• 週次コンテンツリズムを設定（最低週1本）
• コントリビューター向け "good first issue" パイプラインを作成
• 月次コミュニティイベント開催（ハッカソン、AMA）
• 週次でスターベロシティを追跡しチャネル最適化

Gingiris 制作 — @WeiYipei on X で開発者マーケティングのコツを発信中。

GitHub 스타 빠르게 모으기 — 14일 그로스 스프린트

오가닉 발견을 기다리지 마세요. GitHub Trending 진입을 노리는 14일 집중 캠페인입니다. AFFiNE를 0에서 60k+ 스타로 성장시키고 50개 이상의 OSS 프로젝트를 컨설팅한 경험에 기반합니다.

14일 플랜

Phase 1: 기반 구축 (Days 1-3)

Phase 2: 점화 (Days 4-7)

Phase 3: 증폭 (Days 8-11)

Phase 4: 유지 (Days 12-14)

Show HN 전략

효과적인 제목 공식

• "Show HN: [프로덕트] – [8단어 이내 혜택]"
• "Show HN: [X]를 만들었습니다. [공감되는 불만]이라서"
• "Show HN: [X] — [유명 프로덕트]의 오픈소스 대안"

타이밍

• 베스트: 화~목요일, EST 10AM
• 피하기: 주말, 월요일 아침, 금요일 오후
• 1시간에 5포인트 미만이면 1회만 재게시

Reddit 플레이북

OSS에 최적인 서브레딧

밴 방지 규칙

• 직접적인 "스타 눌러주세요" 금지
• 가치를 먼저, 링크는 끝에
• 1시간 내 여러 서브에 포스트하지 않기
• 댓글에 진정성 있게 참여

스타 벨로시티의 과학

• GitHub Trending (일간): 약 50-100스타/일
• GitHub Trending (주간): 3일간 약 200스타
• 알고리즘은 총 개수보다 최근 벨로시티를 중시
• 6시간에 100스타 > 7일에 100스타

스프린트 이후 복리 성장

• 주간 콘텐츠 리듬 설정 (최소 주 1회)
• 컨트리뷰터용 "good first issue" 파이프라인 만들기
• 월간 커뮤니티 이벤트 운영 (해커톤, AMA)
• 주간 스타 벨로시티 추적 및 채널 최적화

Gingiris 제작 — @WeiYipei on X에서 개발자 마케팅 팁 공유 중.

Description: <br>

A 14-day sprint to rapidly grow GitHub stars for your repository, with tactical day-by-day guidance for Show HN, Reddit, Twitter/X threads, and GitHub Trending mechanics. <br>

This skill is ready for commercial/non-commercial use. <br>

Publisher: <br>

gingiris <br>

License/Terms of Use: <br>

MIT-0 <br>

Use Case: <br>

External developers and open-source maintainers use this skill to plan a two-week launch and promotion sprint for increasing GitHub repository visibility, community engagement, and star growth. <br>

Deployment Geography for Use: <br>

Global <br>

Known Risks and Mitigations: <br>

Risk: Marketing advice may conflict with platform-specific community rules or be perceived as spam if applied mechanically. <br> Mitigation: Check each platform's current rules before posting and adapt outreach to genuine, useful technical content. <br> Risk: Growth goals around stars, upvotes, and trending may encourage artificial amplification or direct vote solicitation. <br> Mitigation: Avoid brigading, sockpuppets, spammy reposting, and direct requests for stars or upvotes; prioritize authentic community engagement. <br>

Reference(s): <br>

• English README <br>
• Japanese README <br>
• Korean README <br>
• Gingiris Open Source Skill <br>
• Gingiris Publisher Profile <br>
• WeiYipei on X <br>

Skill Output: <br>

Output Type(s): [guidance, markdown, shell commands] <br> Output Format: [Markdown guidance with tables, bullet lists, and inline shell commands] <br> Output Parameters: [1D] <br> Other Properties Related to Output: [Multilingual reference material is available in English, Japanese, and Korean.] <br>

Skill Version(s): <br>

1.2.2 (source: server evidence release.version) <br>

Ethical Considerations: <br>

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>