extract-session-pr

Extracts session git changes into a new GitHub pull request via worktree commits.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/thisolivier/chronolog --skill extract-session-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract-session-pr
Source: https://github.com/thisolivier/chronolog/tree/main/.claude/skills/extract-session-pr
Command: npx skills add https://github.com/thisolivier/chronolog --skill extract-session-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

It helps you convert the work you produced during the current coding session into a clean pull request while avoiding changes to your working directory.

Core Features & Use Cases

  • Session-to-PR change extraction: Detects modified, staged, untracked, and deleted items, then filters them to the files relevant to your session.
  • Worktree isolation: Creates an isolated git worktree from a chosen base branch so commits and pushes do not touch your current workspace.
  • PR creation automation: Collects PR title and base branch, commits the extracted changes on a new branch, pushes it, and opens a GitHub pull request via the gh CLI.
  • Use case: You finish a feature in your editor but want to keep developing locally; this Skill extracts only the session’s intended changes into a PR that you can review, share, or merge.

Quick Start

Tell the assistant to extract the current session’s changes into a pull request without modifying the working directory.

Frequently Asked Questions about extract-session-pr

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

FAQPage Schema
How do I create a GitHub pull request from my current working session without committing everything?

To create a pull request from your current session without committing everything, this Skill extracts only the relevant modified, staged, new, and deleted files into an isolated git worktree, commits them on a new branch, and pushes them to GitHub. This leaves your working directory untouched so you can continue local development.

Does extracting in-progress work into a PR modify my local working directory?

Extracting in-progress work into a PR does not modify your working directory. The process uses git worktree isolation to apply patches and commit changes on a separate branch, ensuring your current local workspace remains completely intact for continued development.

Do I need the gh CLI installed to automate PR creation from local changes?

Yes, you need the gh CLI installed and available in your environment to automate PR creation from local changes. The Skill validates gh availability before generating a PR branch, pushing commits, and opening the pull request on GitHub.

Can I exclude unrelated files when turning my session into a PR?

Yes, you can exclude unrelated files when turning your session into a PR. The extraction process optionally asks you to filter out modified, staged, untracked, or deleted items that are not part of the intended session work before generating the patch.

What is the best way to share in-progress code changes for review while still editing them locally?

The best way to share in-progress code changes for review while still editing locally is using git worktree isolation. It applies a patch of your session's filtered changes to a new branch, pushes it, creates the PR, and automatically cleans up temporary worktree artifacts.

What happens to temporary git worktrees if the PR creation fails?

If PR creation fails, the temporary git worktrees and patch artifacts are automatically cleaned up. The extraction process ensures that isolated worktree branches and temporary files are removed on both completion and failure, preventing repository clutter.