Use the gh CLI to generate a comprehensive weekly development intelligence report that goes far beyond basic commit summaries.
Data Collection:
- All commits from the past week with full diff analysis
- Pull requests created, reviewed, and merged
- Issues opened, commented on, and closed
- Code review comments given and received
Analysis Points:
- Impact Assessment: Calculate lines of code, files touched, complexity of changes
- Quality Indicators: Identify refactoring vs. new features, bug fixes vs. enhancements
- Architecture Decisions: Highlight any structural changes, new patterns introduced, technical debt addressed
- Collaboration Depth: Analyze review participation, knowledge sharing evidence, cross-team contributions
Productivity Rhythms:
- Peak coding hours and energy patterns
- Task switching frequency (how often you jumped between different areas)
- Focus depth indicators (sustained work on single features vs. scattered contributions)
- Problem-solving approach evolution throughout the week
Learning & Growth Evidence:
- New technologies or patterns experimented with
- Documentation created or improved
- Complex problems tackled vs. routine maintenance
- Skill development indicators in commit progression
Feature Development Context:
- Map commits to product features and business objectives
- Identify which work directly impacts user experience
- Assess technical foundation building vs. immediate feature delivery
- Highlight innovation or creative problem-solving instances
Technical Leadership Indicators:
- Architectural decisions made and their potential impact
- Code quality improvements that benefit the entire team
- Knowledge sharing through comments, documentation, or examples
- Mentoring evidence in code reviews or pair programming artifacts
Create a story that answers:
- What major challenges did you solve this week?
- What new capabilities did you build or improve?
- How did your work advance the product's technical foundation?
- What innovations or creative solutions emerged?
- Where did you demonstrate technical leadership or mentorship?
Trend Analysis:
- Identify patterns in your development approach
- Spot areas where you're building expertise
- Highlight technical investments that will pay dividends
- Flag potential areas needing attention or skill development
Next Week Optimization:
- Based on this week's patterns, suggest productivity optimizations
- Identify knowledge gaps that emerged during the week
- Recommend focus areas for continued growth
- Highlight successful approaches to replicate
- Week's Major Accomplishments: 3-4 high-impact contributions
- Technical Growth Moments: New skills demonstrated or knowledge acquired
- Strategic Impact: How your work advanced broader product/team goals
- Feature Development Breakdown: Detailed analysis of each major feature worked on
- Code Quality Contributions: Refactoring, optimization, and maintainability improvements
- Collaboration Highlights: Meaningful interactions and knowledge sharing instances
- Problem-Solving Showcase: Complex challenges tackled and creative solutions implemented
- Skill Progression: Evidence of learning and capability expansion
- Work Pattern Optimization: Insights into your most productive approaches
- Technical Leadership Growth: Instances where you guided technical decisions or helped others
- Efficiency Metrics: Ratio of impact to effort across different types of work
- Quality Indicators: Code review feedback patterns, bug introduction rates
- Focus Analysis: Deep work vs. reactive work balance
- Innovation Index: Novel approaches or creative solutions introduced
- Compare with previous weeks' patterns (if available)
- Identify improving trends and areas for growth
- Highlight consistency in high-impact work
# Comprehensive data gathering
gh api graphql -f query='
{
viewer {
contributionsCollection(from: "YYYY-MM-DD", to: "YYYY-MM-DD") {
commitContributionsByRepository {
repository { name }
contributions { totalCount }
}
pullRequestContributionsByRepository {
repository { name }
contributions { totalCount }
}
issueContributionsByRepository {
repository { name }
contributions { totalCount }
}
}
}
}'
# Detailed commit analysis with file change patterns
gh api repos/:owner/:repo/commits --since="YYYY-MM-DD" --author="username" | \
jq -r '.[] | "\(.commit.message)\n\(.stats.additions) additions, \(.stats.deletions) deletions\n\(.files | length) files changed\n---"'
# Pull request impact analysis
gh pr list --author="@me" --state="merged" --created="YYYY-MM-DD..YYYY-MM-DD" --json title,additions,deletions,reviewRequests,reviews
# Code review participation
gh api search/issues?q="involves:username+created:YYYY-MM-DD..YYYY-MM-DD+type:pr" --paginateTransform raw data into actionable insights:
- Impact Narrative: Tell the story of what you built and why it matters
- Growth Documentation: Evidence of learning and skill development
- Strategic Alignment: How your technical work supports business objectives
- Leadership Demonstration: Instances of technical decision-making and mentorship
- Innovation Catalog: Creative solutions and novel approaches introduced
If you have access to other tools, correlate:
- Slack activity: Link code changes to discussions and feedback
- Issue tracker: Connect commits to specific problems solved
- Documentation: Identify knowledge sharing and onboarding contributions
- CI/CD metrics: Assess deployment success and system reliability impact
Wow, @brandonkrull can I have permission to link to this from my blog and quote from it? This is AWESOME.