AGENT SKILL

pr-description

Draft a pull request title and description from the commits and diff on the current branch. Use when the user asks to open a PR, write a PR description, or summarize a branch's changes for review.

License 许可
MIT
所属仓库
contextosai/skills
最近更新
2026-10-07
Stars
★ 1
Forks
0

01 前言 Front Matter

name
pr-description
description
Draft a pull request title and description from the commits and diff on the current branch. Use when the user asks to open a PR, write a PR description, or summarize a branch's changes for review.

03 SKILL.md 正文

PR Description

Produce a reviewer-friendly pull request title and body for the current branch.

Steps

  1. Determine the base branch (usually main). Run git log --oneline <base>..HEAD and git diff <base>...HEAD to gather the full set of changes.
  2. Group the changes by theme rather than listing every commit verbatim.
  3. Fill in the template below.

Template

## Summary
<1–3 sentences: what this PR does and why.>

## Changes
- <key change 1>
- <key change 2>

## Testing
<How it was verified — commands run, manual checks, or "not yet tested".>

## Notes for reviewers
<Anything risky, intentionally out of scope, or needing a decision. Omit if none.>

Guidelines

  • Lead with intent: a reviewer should understand the why in the first sentence.
  • Be honest in the Testing section — if something wasn't tested, say so.
  • Keep the bullet list to the changes that matter for review, not noise.
  • Call out breaking changes and migrations explicitly.

04 同仓库更多 Skills

contextosai
contextosai/skills

template-skill

Replace with a description of what this skill does and when Claude should use it.

★ 1
contextosai
contextosai/skills

verify-change

Design and execute a risk-based verification strategy for a software change, bug fix, refactor, migration, configuration update, or release candidate. Use when Codex needs to prove that a change works, choose proportional tests, investigate whether validation is sufficient, or report what remains unverified. Trace claims to evidence across static checks, focused tests, integration boundaries, and runtime behavior instead of merely running the entire test suite.

★ 1
contextosai
contextosai/skills

triage-incident

Triage an active or recent software production incident by establishing impact, stabilizing the system, preserving evidence, building a timestamped timeline, coordinating hypotheses, and choosing reversible mitigations. Use when users report an outage, severe degradation, security or data-integrity event, broken deployment, elevated errors, or ask for incident command, status assessment, mitigation, or investigation support. Prioritize user harm reduction over root-cause completeness and require explicit authority for production mutations.

★ 1
contextosai
contextosai/skills

review-change

Review a code change for concrete correctness, security, data-integrity, compatibility, concurrency, and operability regressions by reconstructing intent and checking affected invariants and boundary paths. Use for local diffs, commits, branches, patches, or pull requests when the user wants actionable review findings. Report only defects introduced or exposed by the change with precise evidence; do not modify code unless asked to address findings.

★ 1
contextosai
contextosai/skills

repo-orient

Map an unfamiliar software repository from code and configuration. Use when Codex needs to understand a new codebase, locate entry points or ownership boundaries, explain architecture and runtime flow, identify where a change belongs, or prepare for implementation without yet modifying files. Produce an evidence-backed repository map, not a directory listing or README paraphrase.

★ 1
contextosai
contextosai/skills

refactor-safely

Restructure existing code while preserving externally observable behavior through explicit invariants, characterization evidence, small reversible steps, and continuous verification. Use when the user asks to refactor, simplify, extract, reorganize, modularize, deduplicate, split a component, improve architecture, or pay down technical debt without intentionally changing product behavior. Distinguish refactoring from feature work and stop scope drift from hiding inside structural edits.

★ 1