pr-implement

Fork-based PR implementation with isolation check. Runs isolation check before starting work. Triggers: "implement PR", "implement contribution", "fork implementation", "code the PR".

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "pr-implement" with this command: npx skills add boshu2/agentops/boshu2-agentops-pr-implement

PR Implement Skill

Fork-based implementation for open source contributions with mandatory isolation check.

Overview

Execute a contribution plan with fork isolation. Ensures PRs are clean and focused by running isolation checks before and during implementation.

Input: Plan artifact from $pr-plan or repo URL

When to Use:

  • Implementing a planned OSS contribution
  • Need isolation enforcement for clean PRs
  • After completing $pr-plan

When NOT to Use:

  • Internal project work (use $implement)
  • Haven't planned yet (run $pr-plan first)

Workflow

-1. Prior Work Check      -> BLOCKING: Check for competing PRs
0.  Input Discovery       -> Find plan artifact or repo
1.  Fork Setup            -> Ensure fork exists and is current
2.  Worktree Creation     -> Create isolated worktree
3.  Isolation Pre-Check   -> BLOCK if mixed concerns
4.  Implementation        -> Execute plan
5.  Isolation Post-Check  -> BLOCK if scope creep
6.  Commit Preparation    -> Stage with proper commit type
7.  Handoff               -> Ready for $pr-prep

Phase -1: Prior Work Check (BLOCKING)

# Search for open PRs on this topic
gh pr list -R <owner/repo> --state open --search "<topic>" --limit 10

# Check target issue status
gh issue view <issue-number> -R <repo> --json state,assignees
FindingAction
Open PR existsCoordinate or wait
Issue assignedCoordinate or find alternative
No competing workProceed

Phase 3: Isolation Pre-Check (BLOCKING)

# Commit type analysis
git log --oneline main..HEAD | sed 's/^[^ ]* //' | grep -oE '^[a-z]+(\([^)]+\))?:' | sort -u

# File theme analysis
git diff --name-only main..HEAD | cut -d'/' -f1-2 | sort -u
CheckPass Criteria
Single commit type0 or 1 prefix
Thematic filesAll match plan scope
Branch freshBased on recent main

DO NOT PROCEED IF PRE-CHECK FAILS.


Phase 4: Implementation

Guidelines

GuidelineWhy
Single concernEach commit = one logical change
Match conventionsFollow project style exactly
Test incrementallyRun tests after each change

Commit Convention

git commit -m "type(scope): brief description

Longer explanation if needed.

Related: #issue-number"

Phase 5: Isolation Post-Check (BLOCKING)

# Commit type analysis
git log --oneline main..HEAD | sed 's/^[^ ]* //' | grep -oE '^[a-z]+(\([^)]+\))?:' | sort -u

# Summary stats
git diff --stat main..HEAD
CheckPass Criteria
Single commit typeAll commits share same prefix
Thematic filesAll files relate to PR scope
Atomic scopeCan explain in one sentence

Phase 7: Handoff

Implementation complete. Isolation checks passed.

Branch: origin/$BRANCH_NAME
Commits: N commits, +X/-Y lines

Next step: $pr-prep

Anti-Patterns

DON'TDO INSTEAD
Skip isolation pre-checkRun Phase 3 FIRST
Skip isolation post-checkRun Phase 5 before push
Mix concerns in commitsOne type prefix per PR
Implement without planRun $pr-plan first

Examples

Implement From Contribution Plan

User says: "Implement this external PR plan with isolation checks."

What happens:

  1. Run pre-checks for branch and scope isolation.
  2. Implement only in planned files/areas.
  3. Run post-checks and prepare handoff for PR prep.

Enforce Single-Concern Commit Set

User says: "Make sure this branch is still single-purpose before I prep the PR."

What happens:

  1. Inspect commit/file patterns against stated scope.
  2. Flag mixed concerns and suggest extraction steps.
  3. Produce a clean handoff to $pr-prep.

Troubleshooting

ProblemCauseSolution
Isolation check failsUnrelated changes on branchMove unrelated edits to separate branch/PR
Commits mix concernsImplementation drifted from planRe-split commits by concern and revalidate
Scope keeps expandingWeak boundaries in planRe-anchor to Out of Scope and stop additional changes
Hard to hand offMissing summary/test contextAdd concise change summary and verification notes

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

codex-team

No summary provided by upstream source.

Repository SourceNeeds Review
256-boshu2
Automation

council

No summary provided by upstream source.

Repository SourceNeeds Review
1.5K-boshu2
Automation

swarm

No summary provided by upstream source.

Repository SourceNeeds Review
281-boshu2
Research

research

No summary provided by upstream source.

Repository SourceNeeds Review
260-boshu2