github-evidence-search

Gathers GitHub commits, PRs, reviews, and issues as performance review evidence.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/EirikHaughom/msconnect-agent --skill github-evidence-search-eirikhaughom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-evidence-search
Source: https://github.com/EirikHaughom/msconnect-agent/tree/main/.github/skills/github-evidence-search
Command: npx skills add https://github.com/EirikHaughom/msconnect-agent --skill github-evidence-search-eirikhaughom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing a performance review requires concrete evidence of your engineering work, but manually digging through months of GitHub activity across multiple repositories is tedious and error-prone. This Skill systematically collects your GitHub contributions and frames them as impact statements mapped to your core priorities. ## Core Features & Use Cases - Multi-Pass Evidence Gathering: Searches pull requests, code reviews given, issues, commits, and discussions month-by-month across user-confirmed work repositories using GitHub MCP tools with GitHub CLI fallback. - Priority Mapping and Impact Framing: Deduplicates results, maps each contribution to core priorities and role accountabilities, and converts raw activity into outcome-focused impact statements. - Use Case: While preparing your Microsoft Connect review, you confirm your work repos, and the Skill compiles a month-by-month evidence pack of merged PRs, reviews, and resolved issues with source links and confidence ratings. ## Quick Start Ask the agent to gather my GitHub contribution evidence for the last six months and map it to my core priorities.

Frequently Asked Questions about github-evidence-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gather GitHub contribution evidence for a performance review?

Confirm your work-related repositories, then run multi-pass searches for PRs, code reviews, issues, and commits month-by-month within the review period. Each item is deduplicated, mapped to your core priorities, and framed as an impact statement with a source link.

How to search GitHub PRs and issues by author and date range?

Use GitHub MCP search_pull_requests and search_issues with queries like author:USERNAME created:>YYYY-MM-DD, or fall back to the GitHub CLI with gh search prs --author @me --created and gh issue list with date filters.

What happens if GitHub MCP tools are unavailable?

The Skill falls back to the GitHub CLI (gh) for equivalent queries. If gh is not installed or authenticated, it notes the gap and asks you to provide GitHub evidence manually rather than fabricating activity.

Does it count lines of code or commit counts as evidence?

No. The Skill explicitly avoids raw activity metrics like lines of code or commit counts. It focuses on shipped outcomes, excludes bot commits and merge commits, and frames every item as an impact statement tied to a priority.

Can it include code reviews I gave to others?

Yes. A dedicated pass collects reviews you gave using reviewed-by queries, capturing review counts, notable architectural feedback, and cross-team reviews as evidence of technical leadership and quality ownership.