prmsg

Generate pull request descriptions from git diffs and session files.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/elfrucool/ai-context-template --skill prmsg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prmsg
Source: https://github.com/elfrucool/ai-context-template/tree/main/core/skills/prmsg
Command: npx skills add https://github.com/elfrucool/ai-context-template --skill prmsg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Producing accurate pull request descriptions for multi-session changes is hard because reviewers need clear context (what and why) that often isn’t fully captured in the final diff.

Core Features & Use Cases

  • Smart JIRA-aware prompting: Always asks whether a JIRA ticket exists, and includes the ticket link when provided.
  • Multi-session context coverage: Detects the scope of changes from git and reads relevant ai-context/sessions/ files to summarize ALL work in scope.
  • PR-template compliant output: Writes a reviewer-friendly PR description following the repository PR format, including a title, summary, detailed change list, and test plan.

Quick Start

Run /prmsg and answer the JIRA questions to generate a copy-paste PR description that incorporates the relevant session context.

Frequently Asked Questions about prmsg

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

FAQPage Schema
How do I generate a pull request description from multi-session git diffs?

To generate a pull request description from multi-session git diffs, run the command and answer the JIRA prompt. It detects scope from local diffs, reads matching session files, and outputs a reviewer-friendly summary.

What is the best way to include multi-session context in a PR description?

The best way to include multi-session context in a PR description is using automated scope detection that reads ai-context session files. It summarizes all relevant work without including commit-by-commit details.

Can I add a JIRA ticket link automatically when creating PR descriptions?

Yes, you can add a JIRA ticket link automatically when creating PR descriptions. The tool always prompts for a JIRA ticket and includes the provided link in the final formatted output.

How do I format a pull request description to include a test plan?

To format a pull request description to include a test plan, the tool applies PR_DESCRIPTION_GUIDELINES to your detected changes. It automatically structures the output with a title, summary, change list, and test plan.

Does the generated PR description include individual commit details?

No, the generated PR description does not include individual commit details. It follows PR_DESCRIPTION_GUIDELINES to omit commit-by-commit information and session metadata, focusing only on the summarized scope of work.