AGENT SKILL

pr

Use when writing a PR body or description — a visual Summary (smallest diagram/diff-sketch/tree that makes the point), concrete Evidence (before/after runs), and Merge Danger (one-way vs two-way door + blast radius). Ported and adapted from mattpocock/skills engineering/pr.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 0
Forks
1

01 前言 Front Matter

name
pr
triggers
[ "user", "model" ]
description
Use when writing a PR body or description — a visual Summary (smallest diagram/diff-sketch/tree that makes the point), concrete Evidence (before/after runs), and Merge Danger (one-way vs two-way door + blast radius). Ported and adapted from mattpocock/skills engineering/pr.

03 SKILL.md 正文

PR

Use this template for the PR body:

## Summary

<diagram, diff-sketch, or tree>

## Evidence

- **Before:** <screenshot/output/failing test run>
  **After:** <screenshot/output/passing test run>

## Merge Danger

**Door:** <one-way or two-way>

**Blast Radius:** <one-word description>

Skip preambles; keep prose brief. Use the repo's domain language (.devin/CONTEXT.md glossary when present).

Summary

Pick the smallest view that makes the key point clear.

  • Logic or algorithm -> pseudocode block.
  • Runtime control flow -> call tree.
  • UI structure -> component tree (include state and module boundaries that matter).
  • File responsibility or broad refactor -> shallow annotated file tree.
  • Interaction/data flow -> Mermaid sequence or flow diagram.
  • The point is what changes -> diff on the shape that already exists (component tree, file tree, call tree, or code block). Show the whole block instead when most of it is new or the user needs a copyable target shape.

Place each visual next to the short text it supports. Keep only the calls, files, props, states, and boundaries needed for the current question. Use one or several; do not overwhelm.

Evidence

Concrete proof the change works, before and after.

  • Screenshots are top tier when the change is visual and the environment supports capture (use computer-use when needed).
  • Execution evidence next: the exact test or command that failed before and passes now — paste real output, not a summary of it.

Merge Danger

Door: one-way or two-way. Two-way doors roll back cheaply; destructive or hard-to-reverse changes are one-way and get a sentence on what makes them irreversible.

Blast Radius: one-word scope of possible impact (e.g. layout shift, consumer breakage, CI contract, migration cost), plus a line when the ramifications aren't obvious.

Cross-skills

  • adaptive-agenda-calendar-routine-engine - Stage 5 versioned delivery (commits, PRs, issue wiring) delegates here together with gh, git-workflows, pr, finishing-a-development-branch.

Cross-skills

  • Use git-github-adaptive-engineering for the full PR pipeline - it owns issue wiring (Closes #N/Refs: #N), --body-file, and density templates; this skill owns the Summary/Evidence/Merge Danger body format.

04 同仓库更多 Skills

Leostruka
Leostruka/devin-bundle

montador-de-ideias

Use when assembling, expanding, or elevating a raw project idea or initial prompt into an ultra-detailed, first-principles dossier and compiled master prompt with journalistic OSINT market research, Tech Lead and Staff Architect justifications, atomic and modular hardening/optimization, and high-impact contact surfaces.

★ 0
Leostruka
Leostruka/devin-bundle

git-github-adaptive-engineering

Use when any task touches git history, GitHub issues/PRs/releases/CI, repo governance, or branch and merge decisions. Runs the Fase Zero situational-awareness battery, picks one of five delivery flows via the adaptive decision engine, and enforces commit/PR information-density standards. Orchestrates the gh, git-workflows, github-actions, pr, and debug/finish skills.

★ 0
Leostruka
Leostruka/devin-bundle

adaptive-agenda-calendar-routine-engine

Use when planning or executing work across hours, days, weeks, or sprints. Turns the calendar into a strict time-blocked agenda (HH:MM-HH:MM blocks carrying a routine profile, expected inputs, and a handoff output artifact), runs the 5-stage cognitive flow (Radar and Hunt -> Triage plus Steve Jobs conception -> workbench manifest -> >=32-cycle loop -> Close plus Open-Minded Scrum), and unfolds macro calendar milestones into micro agenda blocks through extensions/gcal/wrapper.py.

★ 0
Leostruka
Leostruka/devin-bundle

demo

Use when demonstrating a skill in a fixture project.

★ 0
Leostruka
Leostruka/devin-bundle

duplicate-skill

Use when testing duplicate skill name detection.

★ 0
Leostruka
Leostruka/devin-bundle

duplicate-skill

Use when testing duplicate skill name detection.

★ 0