EverCV can now write your weekly engineering report
Most engineers owe someone a weekly status update. A manager, a stakeholder, a client, or themselves. The update almost always gets written the same way: staring at git log for ten minutes, trying to remember what "the thing" was called, then typing four bullet points that don't quite capture the week.
EverCV now handles this.
What it does
POST /api/weekly-report generates a polished weekly engineering report from the data sources you've already connected — GitHub commits, Jira tickets, Linear issues, Google Calendar, ConnectWise time entries, and your done log. It passes the relevant slice of your CV to Claude Haiku, which produces a structured report with four sections:
- Highlights — the 2-4 most impactful things that shipped
- Key deliverables — a concrete bulleted list, referencing actual ticket IDs and feature names
- Blockers & risks — anything that's stalled or recurring (skipped if none)
- Focus next week — inferred from what was in-progress
You pick the week (defaults to the most recently completed Mon–Sun) and the format: Markdown for a README or wiki, HTML for an email client, or Slack mrkdwn for posting directly to a channel.
Email delivery
Set email_me: true and a copy goes to your registered address via SES. Good for people who want a weekly archive of what they shipped, or who need to forward something to a manager without reformatting it.
Why this is a Pro feature
Free users get the daily standup writer (draft yesterday's standup from your CV activity). The weekly report builds on that: it's longer, it uses more CV context, and it's designed for a different audience — a manager or team, not a standup channel. Pro users get both.
The design constraint I kept
The report only includes work that's actually in your CV. No hallucination, no filler. If a week was quiet, it says so. This is intentional — a report that invents impact is worse than no report at all, and the value of a continuous CV is that the raw material is already there, already accurate.
What's next
A scheduled weekly delivery option is the obvious next step — generate and email every Friday at 4pm, no manual trigger required. That's a cron + SES job I'll wire up in a later sprint.
EverCV is in private beta. If you're a senior engineer keeping a continuous work log and want to turn it into automated standups, weekly reports, and AI-powered job tools, get early access.