Dev Loop PR Writer

Use when the user asks to write a pull request description, PR title, PR template, summary of a diff for reviewers or split a large PR. Produces a reviewer-ready PR description with context, changes, testing and risk. Not for reviewing someone's code (use code-review) or release notes (use dev-loop-changelog-generator).

45 stars 6 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill dev-loop-pr-writer
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/dev-loop/pr-writer ~/.claude/skills/dev-loop-pr-writer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# PR Writer

## Purpose
Write effective pull request descriptions — clear, structured, and reviewable — that communicate what changed, why it changed, and how it was validated. Good PR descriptions reduce review time, catch bugs earlier, and create an auditable project history.

## Agent Protocol

### Trigger
Exact user phrases: "write PR", "pull request", "PR description", "PR template", "create PR", "open a PR", "draft PR", "PR summary", "PR title", "write a pull request".

### Input Context
- PR type (feature, bugfix, refactor, chore, docs, hotfix)
- Code changes (files changed, additions/deletions, key modifications)
- Issue or ticket reference (GitHub issue, JIRA, Linear)
- Testing done (unit, integration, manual, E2E)
- Dependencies or breaking changes
- Reviewer notes (areas of concern, decisions made)

### Output Artifact
Pull request with title following convention, structured description, and review guidance.

### Response Format
```
Title: {type(scope): imperative summary}
## What
## Why (Closes #{issue})
## How
## Testing
## Risks / Rollback
## Screenshots (UI only)
```

### Completion Criteria
- [ ] PR title follows Conventional Commits format
- [ ] Description includes what, why, and how
- [ ] Related issues linked
- [ ] Screenshots or screen recordings included (UI changes)
- [ ] Testing methodology described
- [ ] Breaking changes highlighted
- [ ] Deployment considerations noted
- [ ] Reviewers added with specific focus areas
Read the full skill on GitHub

Details

Skill name
dev-loop-pr-writer
Path
skills/dev-loop/pr-writer/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Dev Loop PR Writer skill do?

Use when the user asks to write a pull request description, PR title, PR template, summary of a diff for reviewers or split a large PR. Produces a reviewer-ready PR description with context, changes, testing and risk. Not for reviewing someone's code (use code-review) or release notes (use dev-loop-changelog-generator).

How do I install the Dev Loop PR Writer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill dev-loop-pr-writer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Dev Loop PR Writer popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Devops Gitlab CI

45

j4flmao/agent-skills

Use when the user asks about GitLab CI, .gitlab-ci.yml, stages and needs, rules, parent-child or multi-project pipelines, include templates, CI/CD components, GitLab runners, container builds, or GitLab SAST/DAST scanning. Produces GitLab pipeline configs. Not for GitHub Actions (use github-actions) or Jenkins (use jenkins).

Git & Code Review

Dev Loop Git Workflow

45

j4flmao/agent-skills

Use when the user asks about git branching strategy, trunk-based development vs git flow, rebase vs merge, a messy rebase or merge conflict, commit conventions, squash or history cleanup. Produces team git conventions and commands. Not for multi-team release trains (use enterprise-release-engineering) or changelogs (use dev-loop-changelog-generator).

Git & Code Review

Ecmwf Weather Feedback

23

ecmwf/ecmwf-weather-skills

Turns what a task taught about the ECMWF weather skills into one anonymised, privacy-scanned issue for ecmwf/ecmwf-weather-skills — load this skill first, before running any `gh issue` command or filing, drafting or reporting any issue about these skills. The issue goes to GitHub, or to ECMWF JIRA project AS with the user's own token, or is given as text to paste — shown in full and filed only after an explicit yes, file it. Use when the user wants to send feedback about the ECMWF weather skills, report a problem with a skill or its instructions, suggest an improvement, file an issue for ecmwf

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.