fp-review

Assign commits to issues and post severity-tagged review comments.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/imedu-io/claude_docker_container --skill fp-review-imedu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fp-review
Source: https://github.com/imedu-io/claude_docker_container/tree/main/.claude/skills/fp-review
Command: npx skills add https://github.com/imedu-io/claude_docker_container --skill fp-review-imedu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures commits are properly linked to issue tracker entries and provides structured, actionable code review feedback so reviewers and maintainers can quickly understand changes and their intent.

Core Features & Use Cases

  • Commit-to-issue assignment: Find commits related to an issue and assign or reassign them so history and reviews are traceable.
  • Review commenting and severity tagging: Post targeted review comments with severity prefixes like [blocker], [suggestion], and [nit] to communicate priorities.
  • Interactive reviews and stories: Open diffs in the desktop app for interactive examination and create narrative stories that walk reviewers through the changes.
  • Use case: When preparing a pull request, use this Skill to verify that all relevant commits are assigned to the correct issue, leave file- and line-specific comments, and compose a story summarizing the change for reviewers.

Quick Start

Run fp review <PREFIX>-X to open an interactive review and use fp issue assign to link relevant commits to the issue.

Frequently Asked Questions about fp-review

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

FAQPage Schema
How do I link git commits to issues for better code reviews?

To link git commits to issues, you can use the fp issue assign command to find and map specific commits to their corresponding issue tracker entries. This ensures your repository history and code review process remain traceable to their original intent.

What is the best way to leave structured code review comments with severity levels?

You can leave structured code review comments by posting targeted feedback with severity prefixes like [blocker], [suggestion], and [nit]. This communicates review priorities clearly to maintainers examining repository changes.

Can I perform an interactive code review of repository changes in a desktop app?

Yes, you can open interactive desktop reviews to examine diffs directly. Running the fp review command launches an interactive review session, and you can use the desktop app for story-backed examinations of the repository changes.

Do I need the fp CLI installed to assign commits and review code?

Yes, the fp CLI is required to execute workflows that check commit-to-issue assignments, leave review comments, and create narrative stories. You also need a project initialized with fp and access to git or jj commit history.

Does this code review workflow support Jujutsu repositories or only Git?

This code review workflow supports both Git and Jujutsu repositories. It relies on your existing commit history from either version control system to verify commit-to-issue assignments and generate review feedback.

How do I create a narrative story summarizing code changes for reviewers?

You can create narrative stories that walk reviewers through repository changes by using the interactive review features. This summarizes the change intent and provides a structured walkthrough for maintainers examining the pull request.