engineer-expertise-extractor

Extract an engineer's coding expertise from GitHub contributions via gh.

194|26|Updated Oct 20, 2025

Search Tags:#patterns #best-practices #coding-style

Ready to run

npx skills add https://github.com/jamesrochabrun/skills --skill engineer-expertise-extractor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: engineer-expertise-extractor
Source: https://github.com/jamesrochabrun/skills/tree/main/skills/engineer-expertise-extractor
Command: npx skills add https://github.com/jamesrochabrun/skills --skill engineer-expertise-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Preserve and codify expert knowledge from engineers’ contributions.

Core Features & Use Cases

PR Analysis: Pull-requests review patterns.
Coding Style: Naming, structure, idioms.
Patterns & Best Practices: Documented guidance.
Architectural Decisions: Key tradeoffs.

Quick Start

Provide a GitHub username to analyze and generate a knowledge base.

Frequently Asked Questions about engineer-expertise-extractor

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

FAQPage Schema

How do I extract an engineer's coding expertise from GitHub contributions?▼

Extract coding expertise by analyzing a GitHub username's pull requests, comments, and architectural decisions using GitHub CLI. The Skill identifies coding style, recurring patterns, best practices, code review tendencies, and architectural choices, then outputs a structured engineer profile documenting these elements.

What coding patterns and best practices can I document from pull request analysis?▼

Pull request analysis surfaces naming conventions, code structure idioms, recurring design patterns, architectural tradeoffs, and code review tendencies. These findings get categorized into a knowledge base covering coding_style, patterns, best_practices, architecture, code_review, and example code samples.

Do I need GitHub CLI to analyze an engineer's contributions?▼

Yes, GitHub CLI (gh) is required to fetch pull requests and analyze changes across repositories. The Skill uses gh commands to retrieve PR data, process code changes, and extract the structured expertise profile.

Can I use this to build a knowledge base of engineering practices across organizations?▼

Yes, by analyzing GitHub usernames across multiple organizations, you can extract and codify each engineer's expertise into standardized profile folders. This preserves architectural decisions, coding patterns, and best practices in a structured format for team reference.

What output does the expertise extraction produce?▼

The Skill generates a standardized engineer profile folder structure containing categorized findings: coding style, patterns, best practices, architectural decisions, code review tendencies, and sample code snippets organized for a structured knowledge base.