gitreflect/settings.example.yaml at main · jingyanjiang/gitreflect · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
# ── Author ────────────────────────────────────────────────────────────────────
# Your git email(s) used to filter commits. Supports a list — useful if you
# commit under different identities across repos (work vs. personal email, etc.)
# Leave as [] to auto-detect from `git config user.email` at runtime.
author:
  emails: []
  # emails:
  #   - "you@work.org"
  #   - "you@personal.com"

# ── Repo Paths ────────────────────────────────────────────────────────────────
# List of paths to search for git repos. Both root directories containing many
# repos (e.g. ~/Repos) and specific repo paths (e.g. ~/Repos/my-project) are
# acceptable. All paths are searched recursively — any folder containing .git/
# at any depth will be discovered and offered for selection.
repo_paths:
  - "~/Repos"
  # - "~/work/projects"
  # - "~/side/specific-repo"

# ── Output ────────────────────────────────────────────────────────────────────
# Base directory for all reports. Subdirectories are created automatically:
#   reports_dir/weekly/      ← YYYY-MM-DD-weekly.md
#   reports_dir/monthly/     ← YYYY-MM-monthly.md
#   reports_dir/quarterly/   ← YYYY-Q1-quarterly.md
#   reports_dir/midyear/     ← YYYY-midyear.md
#   reports_dir/yearly/      ← YYYY-yearly.md
# You can override the save path at runtime when the skill prompts you.
output:
  reports_dir: "~/reports"

# ── Weekly Report ─────────────────────────────────────────────────────────────
weekly:
  # date_range controls the default lookback window:
  #   rolling      — last 7 days from today (default)
  #   calendar_week — Mon–Sun of the prior calendar week
  date_range: rolling

  # Template: defines the sections of your weekly report.
  # Each numbered item becomes a section heading in the output.
  # The skill reads these headings to decide which sections need clarifying
  # questions from you (e.g. Meetings cannot be inferred from git history).
  template: |
    1. Technical Work & Project Progress:
    2. Meetings & Collaboration:
    3. Community & Service:
    4. Papers, Talks & Misc:

  # Examples: show the skill what good entries look like for your org/context.
  # These guide tone, length, and level of detail. Add as many as useful.
  # Each example should be a complete weekly report entry (all sections).
  examples:
    - |
      Week ending YYYY-MM-DD

      1. Technical Work & Project Progress:
         - Deployed v2 of the data ingestion pipeline with streaming input support
           to reduce end-to-end latency by ~40%.
         - Migrated authentication layer from session tokens to JWT to meet new
           compliance requirements; updated all downstream service clients.
         - Started prototyping a retrieval-augmented evaluation harness for the
           new model series.

      2. Meetings & Collaboration:
         - Attended weekly project sync and infrastructure planning meeting.
         - Met 1:1 with manager; discussed Q2 roadmap priorities.
         - Joined cross-team call with partner group on shared dataset access.

      3. Community & Service:
         - Reviewed two allocation proposals.
         - Volunteered for departmental STEM outreach event.

      4. Papers, Talks & Misc:
         - Submitted abstract to SC26.
         - Revised benchmark results section of DBaaS paper draft.