Pr Summary

Generate a pull request summary for the current branch

PublishedJun 11, 2026

Loading actions...

5 minBeginnerprompt7 files

Skill content

Main instructions and any bundled files for this skill.

markdown

Additional Files (6)

Generate a pull request summary for the current branch.

Steps

1. Analyze changes

git log main..HEAD --oneline
git diff main...HEAD --stat

2. Generate summary with

What changed and why
Files modified (grouped by area: frontend / backend / architecture / CI / infra)
Breaking changes (if any)
Architecture sync note (if workspace.dsl changed)
Testing notes

3. Format as PR body

## Summary
[1-3 bullet points describing the changes]

## Changes

**Frontend (`src/`)**
- [Changes]

**Backend (`api/`)**
- [Changes]

**Architecture / ADRs**
- [Changes — note if `architecture.json` was regenerated]

**CI / Infra**
- [Changes]

## Test Plan
- [ ] Pre-commit checks pass (lint + dotnet build)
- [ ] Manual smoke test: start `func start` + `swa start`, test affected flow
- [ ] Architecture sync verified (`./Convert-DslToArchitecture.ps1` run if DSL changed)
- [ ] No secrets in staged files

Contents

View Original Source

Related Skills

General

PromptBeginner5 minmarkdown

Untitled Skill

193

Jan 12, 2026

General

PromptBeginner5 minmarkdown

Frontend Typescript Linting.mdc

TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...

160

Feb 15, 2026

General

PromptBeginner5 minmarkdown

2. Apply Deepthink Protocol (reason about dependencies

risks

127

Jan 15, 2026