engineering-coaching

Generate evidence-cited engineering coaching reviews from pull requests, code reviews, issues, and commits.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill engineering-coaching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-coaching
Source: https://github.com/NlightNFotis/skills/tree/main/engineering-coaching
Command: npx skills add https://github.com/NlightNFotis/skills --skill engineering-coaching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a scattered trail of engineering work into a fair, evidence-cited coaching review that focuses on growth instead of judgment. It is designed for situations where you need to identify recurring strengths, weaknesses, and development opportunities from real artifacts such as pull requests, reviews, issues, and commits.

Core Features & Use Cases

  • Evidence-based coaching review: Builds a structured assessment using cited artifacts rather than vague impressions or memory.
  • Pattern detection across work surfaces: Examines PRs, reviews, issues, commits, and related materials to distinguish real behavioral patterns from one-off anecdotes.
  • SWOT plus action planning: Produces a calibrated strengths, weaknesses, opportunities, and threats view, then converts it into a short list of concrete, observable next-step behaviors.
  • Use case: Ideal for quarterly self-review, manager-employee growth conversations, onboarding feedback after a first 90 days, or promotion preparation where the goal is developmental insight rather than formal grading.

Quick Start

Use the engineering-coaching skill to review an engineer’s last six months of PRs, reviews, issues, and commits and produce an evidence-cited SWOT with three prioritized growth actions.

Frequently Asked Questions about engineering-coaching

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

FAQPage Schema
How do I write an evidence-based performance review using GitHub pull requests and commits?

An evidence-based performance review analyzes pull requests, commits, and issues to generate a cited coaching assessment. It clusters behavioral patterns from these artifacts to ensure feedback is grounded in actual work rather than vague memory.

What is the best way to prepare a quarterly self-review from my engineering work?

Preparing a quarterly self-review involves clustering patterns across your pull requests, code reviews, and commits. This process produces a calibrated SWOT analysis with concrete behavioral actions to guide your development conversations.

How does a SWOT analysis work for software engineering career growth?

A SWOT analysis for engineering career growth identifies strengths, weaknesses, opportunities, and threats by examining your work artifacts. It converts these findings into three prioritized, observable behavioral actions with follow-up criteria.

Can I use code review history for onboarding assessment after the first 90 days?

Yes, code review history and pull requests are ideal for 90-day onboarding assessment. Analyzing these artifacts provides developmental insights and calibrated feedback for new engineers instead of formal grading.

How do I generate actionable development goals from GitHub issues and code reviews?

Generating actionable development goals requires clustering observations across GitHub issues and code reviews to detect behavioral patterns. This yields a calibrated assessment with three concrete next-step behaviors and follow-up criteria.

What is the difference between evidence-cited coaching and traditional performance grading?

Evidence-cited coaching focuses on development rather than judgment, using artifact-level citations from pull requests and commits. It calibrates with the engineer to produce growth plans, whereas traditional grading focuses on formal evaluation.