skills.rest
jlissner
jlissnerCOMMUNITY
Explore all skills by this author →
GitHub

grimoire-pr

Generate a PR description from grimoire change artifacts with structured sections.

Updated Jan 26, 2025
Search Tags:#automation#code-review#pull-request#pr-description#change-artifacts#grimoire
One-click install
npx skills add https://github.com/jlissner/lissner.io --skill grimoire-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grimoire-pr
Source: https://github.com/jlissner/lissner.io/tree/main/.claude/skills/grimoire-pr
Command: npx skills add https://github.com/jlissner/lissner.io --skill grimoire-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR workflows often bog down teams when converting grimoire change artifacts into ready-to-submit descriptions. This skill automates that drafting step, saving time and reducing manual errors.

Core Features & Use Cases

  • Generates a complete PR body from manifest.md, tasks.md, feature files, and ADRs.
  • Supports optional post-implementation design review and security considerations.
  • Ensures traceability with a Change ID and preserves consistency with project conventions.

Quick Start

Run the grimoire-pr workflow to generate a PR description from the latest change artifacts.

Frequently Asked Questions about grimoire-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a pull request description from change artifacts automatically?▼

You generate a pull request description by running a workflow that reads change artifacts like manifest.md, tasks.md, feature files, and ADRs. This assembles a structured PR body with sections for summary, changes, scenarios, decisions, and test plans.

What is the best way to structure a PR body for code review using markdown artifacts?▼

Structuring a PR body from markdown artifacts is best handled by preserving a Change ID for traceability and organizing the output into summary, changes, scenarios, decisions, and test plan sections to streamline code reviews.

Can I include security considerations and design reviews in an automated PR description?▼

Yes, you can include optional post-implementation design review and security considerations when generating the PR description. This ensures the structured PR body aligns with project conventions and captures necessary review details.

Do I need manifest.md and tasks.md files to automate my pull request workflow?▼

Yes, you need manifest.md and tasks.md files, along with feature files and ADRs, to automate the pull request workflow. The skill applies when a change has these specific grimoire artifacts and a draft PR or review is requested.

Why does my automated PR draft lack traceability to the original change artifacts?▼

Automated PR drafts lack traceability when the generation process fails to preserve the Change ID. Assembling the PR body directly from the manifest.md and associated artifacts ensures the original change context remains linked.

When should I not use automated code review artifact generation for pull requests?▼

You should not use automated PR description generation when your change lacks the required grimoire artifacts like manifest.md, tasks.md, feature files, or ADRs, as the skill depends on these files to assemble the structured PR body.

Related Skills

Explore More Software Engineering Skills→
CarlosQ96CarlosQ96

create-control-manifest

Generate a flat control manifest from Accepted ADRs and technical preferences.

Community
Advanced
diShine-digital-agencydiShine-digital-agency
1

shine-ship

Automate the ship cycle from branch creation to merged pull request.

Community
Intermediate
jlissnerjlissner

grimoire-pr-review

Review pull requests with multi-persona analysis and structured PR comments.

Community
Advanced
wesleyosantos91wesleyosantos91
6

pr-description

Generate structured Pull Request descriptions from git log and git diff.

Community
Intermediate