> ## Documentation Index > Fetch the complete documentation index at: https://www.opendirectory.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. # product-update-logger > Tell the skill what your product shipped. It writes a polished, living docs/changelog.md entry and hands you a ready-to-use content package: tweet thread, Li... **Category:** Launch · **Version:** `0.0.1` · **Author:** `opendirectory` · **Compatibility:** All targets (claude, codex, opencode, gemini, anti-gravity, openclaw, hermes) Tell the skill what your product shipped. It writes a polished, living `docs/changelog.md` entry and hands you a ready-to-use content package: tweet thread, LinkedIn post, email snippet, and one-liner. Run it after every deploy. Over quarters, `docs/changelog.md` becomes a complete, shareable product history. ## Install ```bash theme={null} npx "@opendirectory.dev/skills" install product-update-logger --target claude ``` ```bash theme={null} npx skills add Varnan-Tech/opendirectory --skill product-update-logger ``` ```bash theme={null} /plugin marketplace add Varnan-Tech/opendirectory /plugin install opendirectory-gtm-skills@opendirectory-marketplace ``` ## What It Does * Accepts: free text items, git commits (auto-read), GitHub PRs -- any combination * Filters noise: merge commits, version bumps, CI/CD, typos excluded automatically * Transforms: technical commit language -> user-facing benefit language * Categorizes: New / Improved / Fixed / Under the hood * Generates a content package: one-liner, tweet thread, LinkedIn post, email snippet * Appends a new dated entry to `docs/changelog.md` (living log, newest entry first) * Saves the content package to `docs/product-updates/[date]-content.md` ## Requirements | Requirement | Purpose | How to Set Up | | - | - | - | | GITHUB\_TOKEN | Optional -- enables GitHub PR fetching for richer context | github.com/settings/tokens (no scopes needed) | No other API keys required. Free text + git auto-read work with no configuration. ## Setup ```bash theme={null} cp .env.example .env # Add GITHUB_TOKEN if you want to pull from GitHub PRs ``` ## How to Use ``` "We shipped dark mode and fixed the export bug this week." "Log my product updates. I'm in a git repo." "We launched 3 things: dark mode, faster search, fixed mobile login." "Log updates from last 14 days. Repo: acme/dashboard" "We shipped the onboarding redesign. Version: v2.1.0" ``` Include competitor names for richer channel discovery. Include ICP role + pain for accurate signal-tracing. ## What Gets Generated ### docs/changelog.md (living log) ```markdown theme={null} # Changelog ## Week of April 23, 2026 ### New - **Dark mode** -- Toggle in Settings > Appearance. Works across all views. ### Improved - **Search** -- Results now load in under half a second. ### Fixed - **CSV export** -- Exports no longer drop the last row. --- ## Week of April 14, 2026 ... ``` ### docs/product-updates/\[date]-content.md (content package) ``` ## One-liner Dark mode, faster search, and a fix for the export bug. ## Tweet Thread [1/4] We shipped 3 things this week. [2/4] Dark mode is live. Toggle it in Settings > Appearance. ... ## LinkedIn Post We shipped 3 updates this week. ... ## Email Snippet Subject: What shipped this week: dark mode + faster search ... ``` ## Input Sources The skill pulls from all three sources automatically: | Source | When used | How to trigger | | - | - | - | | Free text | Always first | Just describe what shipped in your message | | Git commits | Auto-read when in a git repo | Run the skill from your project directory | | GitHub PRs | When GITHUB\_TOKEN + repo provided | Mention "repo: owner/repo" in your message | All three can be combined. Overlapping items are deduplicated. ## Changelog Entry Format Each entry follows a consistent structure: ``` ## [Version label] ### New - **Feature** -- Benefit sentence. ### Improved - **Feature** -- Benefit sentence. ### Fixed - **Feature** -- What was broken, now fixed. ### Under the hood - **Component** -- Developer-relevant change only. ``` Version labels default to `Week of [Month Day, Year]`. Detected semver format is preserved and incremented automatically. ## Content Rules * **Tweets**: Under 280 chars each, no hashtags, no em dashes, active voice * **LinkedIn**: No markdown formatting, no hashtags, founder voice ("We shipped" not "We are excited to announce") * **Email**: 50-100 word body, subject line formula, casual and direct * **One-liner**: Max 20 words, covers top 1-2 items ## Standalone Script Run data collection without Claude. Useful for raw item discovery before analysis. ```bash theme={null} # Git auto-read python3 scripts/gather.py --since 7 --output /tmp/pul-raw.json # Free text items python3 scripts/gather.py --items "Add dark mode|Fix CSV bug" --output /tmp/pul-raw.json # With GitHub PRs GITHUB_TOKEN=your_token python3 scripts/gather.py --repo owner/repo --since 14 # Print to stdout python3 scripts/gather.py --since 7 --stdout | jq '.items' ``` ## Project Structure ``` product-update-logger/ ├── SKILL.md ├── README.md ├── .env.example ├── scripts/ │ └── gather.py git + GitHub + free text collector ├── evals/ │ └── evals.json 5 test cases └── references/ ├── changelog-format.md entry structure, category rules, transformation examples ├── content-rules.md tweet/LinkedIn/email writing rules + banned words └── noise-filter.md git commit patterns to skip ``` ## Cost Per Run * Git, free text: free, no auth * GitHub PRs: free with optional token * AI analysis: uses the model running the skill * Total: free ## License MIT This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.