---
name: langchain-ai-writing-pr-body-title-description
description: "Use when writing or editing a pull request title or body."
license: "MIT"
metadata:
  decimalai-skill-id: "f6059182-1b57-4226-a757-f0eed372fb94"
  decimalai-version-id: "4b7bffa6-41f0-46e2-a3c7-cc482ace3f42"
  decimalai-version: "2"
  decimalai-body-sha256: "a720a83cf138cd0b63e29f0ad3c0255aa914ae62191636fec7d1ccd163ba4b24"
  decimalai-name: "langchain-ai/writing-pr-body-title-description"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "code-review"
  decimalai-source: "https://app.decimal.ai/s/langchain-ai-writing-pr-body-title-description@2/SKILL.md"
---
Keep PR titles and bodies concise; do not write essays. Focus on bullet points, Mermaid diagrams, and useful code samples or snippets. Do not include test-running or validation sections. Do not narrate intermediate PR details; describe the final squash-merge outcome. For visual changes, include a before/after table with uploaded images or videos. In GitHub PR descriptions, always embed screenshots using explicit HTML `<img>` tags with an explicit `width` (for example, `width="640"`), including inside before/after table cells; never use Markdown image syntax. Preserve exact signed image URLs and follow the shared screenshot guidance for published-body, rendered-image, and anonymous GET verification. For benchmarks, always include a before/after table. For truly impressive changes, use a technical-blog style while remaining focused.