pr-logbook

Compose pull request titles, bodies, logbook entries, and squash-merge commit messages.

20|4|Updated May 14, 2026
One-click install
npx skills add https://github.com/crewrig/crewrig --skill pr-logbook-crewrig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-logbook
Source: https://github.com/crewrig/crewrig/tree/main/artifacts/core/skills/pr-logbook
Command: npx skills add https://github.com/crewrig/crewrig --skill pr-logbook-crewrig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn completed work into clear pull requests, logbook updates, and squash-merge messages that match a repository's local conventions.

Core Features & Use Cases

  • PR composition: Drafts concise PR titles and structured bodies for review.
  • Logbook management: Appends or updates logbook entries in the right issue instead of creating duplicate records.
  • Merge-ready messaging: Writes squash-merge commit messages and checks pre-push details like script file permissions.
  • Use case: When a change is ready, use this Skill to produce a reviewer-friendly PR description and the associated logbook entry without missing repository-specific rules.

Quick Start

Ask the skill to prepare a pull request and logbook entry for your finished change.

Frequently Asked Questions about pr-logbook

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

FAQPage Schema
How do I write a pull request description and logbook entry for finished code changes?

You can generate a pull request and logbook entry by asking the Skill to inspect your git log, draft a structured PR body, and append the update to the correct issue while respecting AGENTS.md conventions.

What is a logbook entry in a GitHub review workflow?

A logbook entry tracks completed work by appending updates to the correct issue rather than creating duplicates. This Skill manages that process alongside PR creation to maintain consistent repository records.

Do I need the gh CLI to generate squash-merge commit messages?

Yes, the gh CLI is required. The Skill uses both git and the gh CLI to inspect logs, update PRs, post issue comments, and close issues during the merge and cleanup process.

Can I use this to check script file permissions before pushing a merge commit?

Yes, the Skill checks pre-push details like script file permissions. It also writes squash-merge commit messages that conform to the repository's aggressive conventions before finalizing the merge.

How do I append a logbook entry to an existing GitHub issue without duplicates?

The Skill appends logbook entries by identifying the correct issue and updating it directly via the gh CLI. It follows AGENTS.md review structure to ensure proper issue linkage and prevent duplicate records.

What are the limitations when generating PR titles for repositories without AGENTS.md?

Without AGENTS.md, the Skill cannot apply repository-specific review structures, issue linkage rules, or cleanup conventions, which limits its ability to generate fully compliant PR descriptions and logbook entries.