fiberplane/claude-code-plugins

Overview

This skill ensures commits made during a work session are correctly attributed to FP issues before ending or handing off work. It provides a repeatable commit-to-issue assignment workflow that finds, assigns, and verifies which commits implement which issues so VCS history accurately reflects ownership of changes.

How this skill works

The skill gathers session context by listing in-progress and done issues and recent commits, then launches a focused analysis process that compares commit contents to issue descriptions and changed files. It assigns commits using fp issue assign, verifies assignments with fp issue diff and fp issue files, and surfaces mismatches or ambiguous commits for user action.

When to use it

• At the end of a work session before closing out
• When asked to "review commits", "clean up tracking", or "wrap up work"
• Before handing off code to another agent or person
• When multiple issues were touched and commits may be mixed
• If you want a clear VCS-to-issue attribution audit

Best practices

• List in-progress and recently done issues first to build context
• Inspect recent commit details (jj show or git show) before assigning
• Match by files changed, commit message, and issue requirements—not just timestamps
• Assign a commit to the primary issue if it spans multiple issues, and note the overlap in the issue comment
• Create or use a maintenance/catch-all issue for orphan commits when appropriate

Example use cases

• Finish a sprint day: ensure all day’s commits are assigned to the right FP issues
• After a feature branch: reconcile mixed commits that touch several issues
• Handing off to another agent: verify tracking so the recipient knows what work belongs where
• Cleanup pass when commit messages are vague or work was bundled into large commits
• Detect orphaned changes and create a new issue for maintenance or follow-up