engineer-snapshot

Engineer Snapshot

Generate a per-engineer activity snapshot combining JIRA issues, GitHub PR activity, and open action items from 1:1 notes.

Prerequisites

• acli must be installed and authenticated (acli jira auth)
• gh CLI must be installed and authenticated (gh auth login)
• jq and yq must be installed and available in PATH
• A team config YAML file (see Config Format below)

Config Format

Create a YAML file with your team's details (same format as team-weekly-report):

team:
  name: "My Team"
  jira:
    url: "https://mycompany.atlassian.net"
    project: "PROJ"
    component: "MyComponent"  # optional
  github:
    repositories:
      - "org/repo1"
      - "org/repo2"
  members:
    - name: "Engineer One"
      jira_username: "712020:account-id-here"
      github_username: "eng1"
      notes_file: "notes/engineer_one.md"  # optional
defaults:
  jira_lookback_days: 7
  github_lookback_days: 7
  stale_threshold_days: 7

Implementation

Step 1: Parse Arguments

Parse $ARGUMENTS for:

• Engineer name (required): first positional argument
• --config PATH (required): path to team config YAML
• --jira-days N (optional): JIRA lookback for stale threshold
• --github-days N (optional): GitHub lookback for merged PRs

If the engineer name is missing, ask:

"Which engineer should I generate a snapshot for?"

If --config is missing, ask:

"Which team config file should I use? Provide the path to your YAML config file."

Step 2: Load Config

Read the config file to extract the engineer's details:

• github_username — needed for GitHub PR queries
• notes_file — path to 1:1 notes (if configured)
• team.github.repositories — repos to search for PRs
• defaults.github_lookback_days — fallback for --github-days

Step 3: Fetch JIRA Data

Run the JIRA fetch script to get active and blocked issues:

"${CLAUDE_SKILL_DIR}/scripts/fetch_engineer_jira.sh" \
  --config <CONFIG_PATH> \
  --engineer "<ENGINEER_NAME>"