ship-digest_skill

Overview

This skill detects new GitHub repositories you pushed today and turns them into concise, technical ship announcements ready for social media. It analyzes README, recent commits, and the repo file tree to produce a technical digest plus two draft posts (Twitter/Reddit style) for approval. The skill never auto-posts; it waits for your confirmation before sending to a posting skill.

How this skill works

It fetches your repos sorted by pushed_at and compares them to a local state file to identify new activity. For repos pushed today (or with 3+ new commits since last check) it extracts README content, recent commits, and file paths to infer purpose and tech stack. It then composes a short technical digest and two hook-driven social drafts, and returns them for your review.

When to use it

• You want a daily summary of what you shipped on GitHub without manually inspecting repos.
• You need ready-to-edit social announcements after a code push or release.
• You maintain multiple projects and want automated detection of new work pushed today.
• You prefer reviewing drafts before any social posting (no automatic publishing).

Best practices

• Set GITHUB_USERNAME as an environment variable for reliable detection.
• Keep README and recent commit messages clear to improve digest quality.
• Run the cron schedule twice daily or trigger manually after a ship.
• Review both draft options and pick edits that preserve first-person, authentic voice.
• Avoid banned words in your final post; the skill excludes them by default.

Example use cases

• A solo founder pushes a new microservice and wants a quick technical announcement for Twitter and Reddit.
• An indie hacker releases a CLI tool and needs a compact digest including lines of code and supported platforms.
• A growth engineer ships a performance tweak and wants a data-hook post highlighting the improvement metric.
• A maintainer publishes a library update and wants two draft hooks (story and contrarian) to choose from.