Weekly Wins Journal

Captures and celebrates your weekly accomplishments by pulling data from git commits, completed tasks, calendar events, and manual entries. Designed to combat the common feeling of "I did not get enough done this week" by surfacing concrete evidence of your progress. Integrates with GitHub, GitLab, Todoist, Jira, Linear, Google Calendar, and local git repositories.

Supported Platforms & Integrations

Platform	Setup Method	Auth Type	Notes
GitHub	GitHub API / gh CLI	OAuth or PAT	Commits, PRs merged, issues closed
GitLab	GitLab API	Personal access token	MRs merged, issues resolved, pipelines
Todoist	Todoist REST API	API token	Completed tasks with project context
Jira	Jira Cloud REST API	API token + email	Issues transitioned to Done

When to Use This Skill

• Use this when you feel unproductive despite working hard all week
• Use this when you want automated evidence of progress for performance reviews
• Use this when you want a weekly reflection practice grounded in data, not memory
• Consider alternatives when you need daily tracking (use daily-habit-scorecard)

Quick Start

Copy
# Minimal configuration - weekly-wins.yml
skill: weekly-wins-journal
schedule: "friday-17:00"
sources:
  github:
    username: "yourusername"
    repos: ["project-a", "project-b"]
    include: ["commits", "prs_merged", "issues_closed", "reviews"]
  todoist:
    api_token_env: "TODOIST_API_TOKEN"
    projects: ["Work", "Side Project"]
  calendar:
    provider: google
    calendars: ["primary"]
    count_meetings: true

Copy
claude /weekly-wins-journal

Expected Output

WEEKLY WINS JOURNAL - Week of March 9-15, 2026
Week 11 of 2026 | Win streak: 8 consecutive weeks logged

CODE CONTRIBUTIONS:
  Commits: 34 across 2 repositories
  Pull Requests merged: 5
    - #312: Implement user authentication flow (project-a)
    - #318: Add rate limiting middleware (project-a)
    - #320: Fix memory leak in WebSocket handler (project-a)
    - #45: Setup CI/CD pipeline (project-b)
    - #47: Add unit tests for payment module (project-b)
  Issues closed: 3
  Code reviews completed: 7
  Lines changed: +2,847 / -891
...

Advanced Configuration

Platform-Specific Setup

GitHub Detailed Config

Copy
sources:
  github:
    username: "yourusername"
    token_env: "GITHUB_TOKEN"
    repos: ["org/repo-a", "org/repo-b"]
    include:
      - commits
      - prs_merged

Full Options Reference

Parameter	Type	Default	Description
schedule	string	"friday-17:00"	When to generate the wins journal
sources	object	required	Data source configurations
manual_wins	boolean	true	Prompt for manual win entries
lookback_days	number	7	Days to look back for wins
highlight_threshold	number	500	Lines changed to flag as highlight PR
include_metrics	boolean	true	Show quantitative metrics (commits, LOC)

Core Concepts

Concept	Purpose	How It Works
Multi-Source Aggregation	Captures all work, not just what you remember	Pulls from code, tasks, calendar, and manual input for complete picture
Highlight Detection	Surfaces your biggest wins automatically	Identifies large PRs, milestone completions, and resolved long-standing issues
Negativity Bias Counter	Fights "I did nothing" feeling	Quantitative evidence makes it impossible to discount your actual output
Energy Mapping	Reveals productivity patterns	Analyzes which days and times produced the most output

Architecture

GitHub API ──────> Git Analyzer ────┐
  GitLab API ─────> Merge Analyzer ──┤
  Todoist API ────> Task Aggregator ──┼──> Win Collector ──> Highlight Detector

Workflow Examples

Scenario 1: End-of-quarter performance review prep

Input: Run --quarterly to aggregate 13 weeks of wins journals Processing: Aggregates all weekly wins into categorized quarterly summary. Calculates total commits, PRs, tasks completed. Identifies top 5 highlights. Generates narrative suitable for self-review forms. Output: Structured quarterly achievements document with metrics, highlights, and growth narrative. Copy-paste ready for performance review systems.

Scenario 2: First week at a new job

Input: Only 8 commits (onboarding), 3 tasks (setup-related), many meetings Processing: Detects low code output + high meeting count pattern consistent with onboarding. Reframes wins around learning: repos cloned, environments set up, team members met, first PR submitted. Output: Wins framed as onboarding progress with "First week milestones" section celebrating setup completion and first contributions.

Best Practices

1. Run it every Friday without fail -- Consistency creates a valuable archive. Even on light weeks, the act of reviewing accomplishments resets your mindset for the.

2. Always add 2-3 manual wins -- Automated sources capture what you did but miss how you grew. Manual entries like "handled a difficult conversation well" or.

3. Use the shareable format for manager updates -- The shareable version strips personal notes and reformats wins as professional status updates. This saves 20 minutes of weekly.

Common Issues

1. GitHub showing commits from other team members -- Ensure the username field matches your exact GitHub username. For organization repos, the skill filters by author. Verify with.

2. Todoist showing tasks from wrong week -- Todoist's "completed" timestamp may differ from your timezone. Set timezone explicitly in the config to match your Todoist.

Privacy & Data Handling

Win data is aggregated locally from your authenticated API sources. No win content, commit messages, or task descriptions are shared with external services beyond the source APIs. The journal files are stored in your configured output_path as plain markdown. When using the shareable format, you control what gets shared -- the skill generates the document locally and you decide how to distribute it.