weekly-shiplog

Generate weekly narrative shiplogs from commits, merged PRs, releases, and closed issues.

6|2|Updated May 21, 2026

Search Tags:#content generation #autonomous agents #gitHub #weekly updates #shiplog #release reporting #theme filtering

Ready to run

npx skills add https://github.com/anajuliabit/aeon --skill weekly-shiplog-anajuliabit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: weekly-shiplog
Source: https://github.com/anajuliabit/aeon/tree/main/skills/weekly-shiplog
Command: npx skills add https://github.com/anajuliabit/aeon --skill weekly-shiplog-anajuliabit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It saves teams from manually writing weekly status updates by automatically collecting recent shipping activity (commits, merged PRs, releases, and closed issues) and turning it into a narrative shiplog article.

Core Features & Use Cases

Weekly shipping narrative generation: Creates either a full or short “Week in Review” article based on the volume and substance of recent changes.
Theme-filtered updates: Optionally narrows the shiplog to a specific topic by matching commit/PR messages and changed file paths against a provided theme.
Idempotent daily output: Writes at most one shiplog per day and avoids duplicate runs by checking for an existing article.
Source-backed reporting: Grounds every concrete claim with exact (sha) and (#PR) references derived from GitHub API data.

Quick Start

Run weekly-shiplog with the optional theme filter so the update focuses on the topic you care about.

Frequently Asked Questions about weekly-shiplog

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

FAQPage Schema

How do I automate weekly shipping updates from GitHub commits and pull requests?▼

Automating weekly shipping updates involves aggregating commits, merged pull requests, releases, and closed issues from watched repositories over a rolling 7-day window to generate a narrative summary. This process turns raw GitHub activity into a structured shiplog article for stakeholders.

Can I filter a GitHub release report to only include changes related to a specific theme?▼

Yes, you can filter a GitHub release report by matching commit and pull request messages alongside changed file paths against a provided theme. This narrows the weekly shiplog narrative to focus exclusively on the specific topic you care about.

What is the best way to ensure automated weekly reports do not generate duplicate entries?▼

To prevent duplicate weekly reports, the generation process enforces idempotency by checking for an existing daily article before creating a new one. This ensures at most one shiplog is written per day, avoiding redundant outputs across automated runs.

How do I create source-backed weekly engineering summaries for stakeholders?▼

Creating source-backed engineering summaries grounds every concrete claim in the narrative with exact (sha) and (#PR) references derived from GitHub API data. This provides product and community stakeholders with verifiable, consistent shipping updates.

Does weekly shiplog generation require agent memory inputs for watched repositories?▼

Yes, generating the weekly shiplog requires reading agent memory inputs to identify watched repositories and access prior context or logs. This memory data is necessary to compute shipping signals and theme clusters for the final report.