team-weekly-report

Team Weekly Report

Generate a comprehensive weekly status report for an engineering team by combining JIRA issue data and GitHub PR activity.

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:

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"
    - name: "Engineer Two"
      jira_username: "712020:account-id-here"
      github_username: "eng2"
defaults:
  jira_lookback_days: 7
  github_lookback_days: 7
  stale_threshold_days: 7

Finding JIRA account IDs: In Jira Cloud, go to a user's profile page. The account ID is the long string in the URL after /people/.

Implementation

Step 1: Determine Config Path

Parse $ARGUMENTS for the --config flag and optional --days flag.

If no --config is provided, ask the user:

"Which team config file should I use? Provide the path to your YAML config file (e.g., ~/team-config.yaml)."

Validate the config file exists before proceeding.

Step 2: Fetch JIRA Data

Run the JIRA fetch script to collect closed, open, stale, and blocked issues for every team member:

"${CLAUDE_SKILL_DIR}/scripts/fetch_team_jira.sh" --config <CONFIG_PATH> --days <N>

The script outputs JSON to stdout with a members array. Each member entry contains closed_issues, open_issues, stale_issues, and blocked_issues arrays. Capture the full JSON output for analysis.

If the script fails, display the error and stop.

Step 3: Fetch GitHub Data

Run the GitHub fetch script to collect open and merged PRs for every team member across the configured repositories: