analyst:impact

Generate business and technical impact reports for GitHub Pull Requests.

Updated Feb 24, 2026

Search Tags:#automation #code review #pull request #github #impact analysis #reporting

Ready to run

npx skills add https://github.com/atournayre/claude-personas --skill analyst-impact

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyst:impact
Source: https://github.com/atournayre/claude-personas/tree/main/analyst/skills/impact
Command: npx skills add https://github.com/atournayre/claude-personas --skill analyst-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive business and technical impact reports for GitHub Pull Requests, streamlining the review process.

Core Features & Use Cases

Automated Reporting: Generates detailed business and technical impact analyses for PRs.
Integration: Automatically adds these reports to the PR description for easy visibility.
Use Case: Before merging a code change, automatically generate reports detailing its business implications (e.g., user impact, risk) and technical implications (e.g., code metrics, security concerns).

Quick Start

Run the analyst impact skill for pull request number 123.

Frequently Asked Questions about analyst:impact

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

FAQPage Schema

How do I generate an impact analysis report for a GitHub pull request?▼

You can generate a pull request impact analysis report by running the skill with a specific PR number. It analyzes modified files, dependencies, and tests to produce structured business and technical reports, integrating them directly into the PR description.

What is PR impact analysis and why do I need it before merging code?▼

PR impact analysis evaluates the business and technical implications of a code change before merging. It assesses user impact, risk, code metrics, and security concerns, helping reviewers understand the full scope and potential consequences of the modification.

How do I automatically add an impact report to a GitHub PR description?▼

To automatically add an impact report to a GitHub PR description, run this skill on the target pull request. It generates the analysis and integrates the findings directly into the PR description text for immediate reviewer visibility.

Can I analyze pull request dependencies and tests without manual code review?▼

Yes, you can analyze pull request dependencies and tests automatically. The skill examines modified files, dependency chains, and test structures to generate comprehensive technical impact findings without requiring manual inspection of each file.

Does GitHub PR impact reporting work for both business and technical metrics?▼

Yes, GitHub PR impact reporting covers both business and technical metrics. It evaluates business implications like user impact and risk alongside technical details such as code metrics and security concerns, providing a complete assessment of the change.

What is the best way to document code changes and risk in a pull request?▼

The best way to document code changes and risk in a pull request is to automate impact reporting. This skill generates detailed business and technical analyses and saves them locally while adding the structured findings directly to the PR description.