pr-implement▌
boshu2/agentops · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Fork-based implementation for open source contributions with mandatory isolation check.
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-planfirst)
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
| Finding | Action |
|---|---|
| Open PR exists | Coordinate or wait |
| Issue assigned | Coordinate or find alternative |
| No competing work | Proceed |
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
| Check | Pass Criteria |
|---|---|
| Single commit type | 0 or 1 prefix |
| Thematic files | All match plan scope |
| Branch fresh | Based on recent main |
DO NOT PROCEED IF PRE-CHECK FAILS.
Phase 4: Implementation
Guidelines
| Guideline | Why |
|---|---|
| Single concern | Each commit = one logical change |
| Match conventions | Follow project style exactly |
| Test incrementally | Run 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
| Check | Pass Criteria |
|---|---|
| Single commit type | All commits share same prefix |
| Thematic files | All files relate to PR scope |
| Atomic scope | Can 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'T | DO INSTEAD |
|---|---|
| Skip isolation pre-check | Run Phase 3 FIRST |
| Skip isolation post-check | Run Phase 5 before push |
| Mix concerns in commits | One type prefix per PR |
| Implement without plan | Run $pr-plan first |
Examples
Implement From Contribution Plan
User says: "Implement this external PR plan with isolation checks."
What happens:
- Run pre-checks for branch and scope isolation.
- Implement only in planned files/areas.
- 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:
- Inspect commit/file patterns against stated scope.
- Flag mixed concerns and suggest extraction steps.
- Produce a clean handoff to
$pr-prep.
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Isolation check fails | Unrelated changes on branch | Move unrelated edits to separate branch/PR |
| Commits mix concerns | Implementation drifted from plan | Re-split commits by concern and revalidate |
| Scope keeps expanding | Weak boundaries in plan | Re-anchor to Out of Scope and stop additional changes |
| Hard to hand off | Missing summary/test context | Add concise change summary and verification notes |
How to use pr-implement on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add pr-implement
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches pr-implement from GitHub repository boshu2/agentops and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate pr-implement. Access the skill through slash commands (e.g., /pr-implement) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★25 reviews- ★★★★★Yash Thakker· Sep 17, 2024
pr-implement fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Amina Srinivasan· Sep 5, 2024
pr-implement reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Rahul Santra· Sep 1, 2024
Solid pick for teams standardizing on skills: pr-implement is focused, and the summary matches what you get after install.
- ★★★★★Arya Park· Sep 1, 2024
pr-implement has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Noah Srinivasan· Aug 24, 2024
I recommend pr-implement for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Pratham Ware· Aug 20, 2024
We added pr-implement from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Dev Jackson· Aug 20, 2024
Keeps context tight: pr-implement is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dhruvi Jain· Aug 8, 2024
Registry listing for pr-implement matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Oshnikdeep· Jul 27, 2024
pr-implement reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Benjamin Perez· Jul 15, 2024
pr-implement fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 25