Gh Daily

Cross-Platform AI Agent Skill This skill works with any AI agent platform that supports the skills.sh standard.

GitHub Daily - Standup Meeting Preparation

Smart standup report generator that analyzes GitHub Issues activity, pull requests, notifications, and git history to provide structured updates for daily meetings.

Anti-Hallucination Guidelines

CRITICAL: Standup reports must reflect ACTUAL work done:

•Only list real issues - Every issue/PR must come from gh CLI output
•Verify completion - Only mark as "Completed" if state is closed or PR is merged
•Real commit counts - Use actual git log output, never estimate
•Actual blockers - Only mention blockers explicitly labeled or commented in GitHub
•True metrics - All numbers from actual GitHub and git data

Context Detection

Phase 1: Determine Repository and User

Detect the working context in order of priority:

•Command argument: --repo owner/repo or -r owner/repo
•Current git remote: Parse from git remote get-url origin
•gh CLI default: Use gh repo view --json nameWithOwner -q .nameWithOwner

bash

# Detect current repo from git remote
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null)
if [ -z "$REPO" ]; then
 echo "ERROR: Not in a GitHub repository. Use --repo owner/repo to specify."
fi
echo "Detected repo: $REPO"

# Detect authenticated user
GH_USER=$(gh api user -q .login 2>/dev/null)
echo "Authenticated as: $GH_USER"
If no repo is detected and none provided, ask the user to specify with `--repo owner/repo`.

If the user works across multiple repos, offer to scan all repos where they have recent activity:
```bash
# Find repos with recent activity (issues assigned to user)
gh search issues --assignee @me --state open --limit 20 --json repository --jq '[.[].repository.nameWithOwner] | unique | .[]'
## Workflow

### Phase 2: Calculate Date Range

```bash
# Calculate since date (yesterday, or Friday if today is Monday)
if [[ $(date +%u) == 1 ]]; then
 # Monday - report from Friday
 SINCE_DATE=$(date -v-3d +%Y-%m-%d 2>/dev/null || date -d "3 days ago" +%Y-%m-%d)
else
 # Other days - report from yesterday
 SINCE_DATE=$(date -v-1d +%Y-%m-%d 2>/dev/null || date -d "yesterday" +%Y-%m-%d)
fi
echo "Reporting since: $SINCE_DATE"
### Phase 3: Gather Activity Data

```bash
# Get issues assigned to me (open)
gh issue list --assignee @me --state open --json number,title,state,labels,milestone,updatedAt,createdAt --limit 50

# Get issues closed recently (by me)
gh issue list --assignee @me --state closed --json number,title,state,labels,closedAt,milestone --limit 20 | jq --arg since "$SINCE_DATE" '[.[] | select(.closedAt >= $since)]'

# Get PRs authored by me (open)
gh pr list --author @me --state open --json number,title,state,reviewDecision,isDraft,labels,updatedAt --limit 30

# Get PRs merged recently
gh pr list --author @me --state merged --json number,title,mergedAt,labels --limit 20 | jq --arg since "$SINCE_DATE" '[.[] | select(.mergedAt >= $since)]'

# Get PRs where my review is requested
gh pr list --search "review-requested:@me" --state open --json number,title,author,updatedAt,labels --limit 20

# Get notifications (mentions, review requests, assignments)
gh api notifications --jq '.[] | select(.unread == true) | {reason: .reason, title: .subject.title, type: .subject.type, url: .subject.url}'

# Get git activity
git log --author="$(git config user.email)" --since="$SINCE_DATE" --oneline --all --no-merges

# Count commits and files changed
git rev-list --count --since="$SINCE_DATE" --author="$(git config user.email)" --all 2>/dev/null || echo "0"
git diff --stat $(git log --since="$SINCE_DATE" --author="$(git config user.email)" --format=%H --all | tail -1)..HEAD --shortstat 2>/dev/null
### Phase 4: Analyze with SubAgents (For Comprehensive Reports)

For detailed format, use parallel analysis:

Agent 1 - Work Classification:

•prompt: "Classify these GitHub issues and PRs into: Completed (closed/merged since date), In Progress (open, recently updated), Blocked (has 'blocked' label or mentioned in comments), Review Needed (PRs awaiting review). Base ONLY on actual state/label fields. Return categorized list."
•agent-type: "general-purpose"

Agent 2 - Impact Analysis:

•prompt: "For completed issues and merged PRs, summarize the business/technical impact based on title, labels, and milestone context. Keep it factual."
•agent-type: "general-purpose"

Agent 3 - Git Correlation:

•prompt: "Match git commits to GitHub issues/PRs by issue number in commit messages (e.g., #123, fixes #456). Report which issues have code changes and quantify work per issue."
•agent-type: "Explore"

Phase 5: Generate Report

Track sections completed with TodoWrite.

Priority Scoring

When analyzing issues, score them using these factors:

•Label Priority: priority: critical or P0 = x10, priority: high or P1 = x7, priority: medium or P2 = x4
•Milestone Proximity: Days until milestone due date (lower = higher score)
•Issue Age: Stale issues (>7 days no update) get flagged
•Blocking Status: Has blocked or blocking label = +5 points
•Review Requested: PRs where your review is pending = +3 points
•Bug vs Feature: Issues labeled bug with high priority = +4 points
•Mentions/Comments: Recent @mentions or comments = +2 points

Output Formats

For detailed output format templates (default, brief, slack), see references/output-formats.md.

Available formats:

•Default (Detailed): Full report with completed work, in-progress items, PRs, blockers, metrics, and schedule
•Brief (--format brief): Concise one-line-per-section format for quick standups
•Slack (--format slack): Formatted for Slack/Teams posting with markdown

Command Options

`--repo <owner/repo>` or `-r <owner/repo>`

Specify the GitHub repository explicitly.