learn-gw-pr

Create a GitHub pull request and link it to a ProjSight task.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/novel-jp/projsight-plugin --skill learn-gw-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn-gw-pr
Source: https://github.com/novel-jp/projsight-plugin/tree/main/skills/learn-gw-pr
Command: npx skills add https://github.com/novel-jp/projsight-plugin --skill learn-gw-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill teaches how to turn a completed branch into a pull request and connect it to a ProjSight task so review work stays traceable and coordinated.

Core Features & Use Cases

  • PR creation workflow: Prepare a branch, commit changes, push to GitHub, and create a pull request with a clear summary and test plan.
  • Task linkage in ProjSight: Attach the PR URL to the related task and move the task into review status.
  • Review handoff practice: Learn the exact sequence used by teams and AI agents to trigger reviewer notifications and preserve work context.

Quick Start

Follow the ProjSight PR flow for your learning workspace, create a pull request for your branch, attach it to the matching task, and mark the task as in review.

Frequently Asked Questions about learn-gw-pr

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

FAQPage Schema
How do I create a GitHub pull request and link it to a ProjSight task for review tracking?

To create a pull request and link it for review tracking, you push your Git branch to GitHub, run gh pr create with a summary, attach the PR URL to the ProjSight task, and update the task status to in_review.

What is the correct git workflow for moving a ProjSight task into review status?

The correct git workflow for moving a ProjSight task into review status involves committing changes to a branch, creating a GitHub pull request, and using upsert_task(status: 'in_review') after attaching the PR to preserve work context and trigger notifications.

How does attaching a pull request to a task improve code review handoffs?

Attaching a pull request to a task improves code review handoffs by keeping branch updates, PR descriptions, and task status synchronized, which ensures reviewers receive notifications and trace work back to the original ProjSight task.

Do I need the GitHub CLI to create pull requests in a ProjSight workflow?

Yes, you need the GitHub CLI to create pull requests in a ProjSight workflow because the process requires running the gh pr create command to generate the PR URL before attaching it to the task.

What steps are required to complete the review handoff when creating a PR?

Completing the review handoff when creating a PR requires three steps: running gh pr create, using attach_pr to link the URL to the task, and calling upsert_task(status: 'in_review') to finalize the notification flow.

Can I use this pull request creation flow for team projects outside of GitHub?

No, you cannot use this pull request creation flow for team projects outside of GitHub because the workflow specifically relies on GitHub-based branch synchronization and the gh pr create command to generate and link pull requests.