pr-logbook

Generate PR titles, bodies, and linked logbook entries from code changes.

3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hcross/crewrig --skill pr-logbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-logbook
Source: https://github.com/hcross/crewrig/tree/main/.gemini/skills/pr-logbook
Command: npx skills add https://github.com/hcross/crewrig --skill pr-logbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs and logbook workflows frequently spin up manually, causing miscommunication and friction during code changes and project tracking.

Core Features & Use Cases

  • Automates PR title and body generation based on diffs and conventions (AGENTS.md).
  • Generates structured logbook entries linked to the PR and issue.
  • Enforces project conventions and templates for reviewers and agents.
  • Use Case: When you open or update a PR, the skill produces a ready-to-review title, body, and a linked logbook entry.

Quick Start

Draft a PR title and body from the current changes and generate a linked logbook entry following AGENTS.md conventions.

Frequently Asked Questions about pr-logbook

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

FAQPage Schema
How do I automate pull request title and body generation from code diffs?

You can automate pull request generation by evaluating code diffs and PR context to produce ready-to-review titles and bodies. It applies AGENTS.md conventions to ensure PR structure complies with project templates for reviewers and agents.

How do I create structured logbook entries linked to a GitHub pull request?

Creating structured logbook entries linked to a GitHub pull request captures PR and issue context to generate formatted tracking records. It enforces logbook formatting conventions defined in AGENTS.md for accurate project tracking.

Can I update existing PR descriptions automatically in GitHub workflows?

You can update existing PR descriptions automatically in GitHub workflows by processing updated code changes and PR context. It regenerates compliant PR bodies and appends linked logbook entries following AGENTS.md conventions.

Do I need AGENTS.md conventions to enforce PR templates and logbook formatting?

You need AGENTS.md conventions to enforce PR templates and logbook formatting because the generation process relies on them for structure. It uses these project conventions to ensure all PR titles, bodies, and logbook entries remain compliant.

What is the best way to enforce code review templates for GitHub pull requests?

The best way to enforce code review templates for GitHub pull requests is automating generation from diffs using AGENTS.md conventions. It produces standardized titles, bodies, and linked logbook entries to reduce friction during code changes.