Fork-based implementation for open source contributions with mandatory isolation check.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpr-implementExecute the skills CLI command in your project's root directory to begin installation:
Fetches pr-implement from boshu2/agentops and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pr-implement. Access via /pr-implement in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
260
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
260
stars
Fork-based implementation for open source contributions with mandatory isolation check.
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:
$pr-planWhen NOT to Use:
$implement)$pr-plan first)-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
# 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 |
# 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.
| Guideline | Why |
|---|---|
| Single concern | Each commit = one logical change |
| Match conventions | Follow project style exactly |
| Test incrementally | Run tests after each change |
git commit -m "type(scope): brief description
Longer explanation if needed.
Related: #issue-number"
# 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 |
Implementation complete. Isolation checks passed.
Branch: origin/$BRANCH_NAME
Commits: N commits, +X/-Y lines
Next step: $pr-prep
| 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 |
User says: "Implement this external PR plan with isolation checks."
What happens:
User says: "Make sure this branch is still single-purpose before I prep the PR."
What happens:
$pr-prep.| 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 |
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
pr-implement fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
pr-implement reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: pr-implement is focused, and the summary matches what you get after install.
pr-implement has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend pr-implement for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added pr-implement from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: pr-implement is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for pr-implement matched our evaluation — installs cleanly and behaves as described in the markdown.
pr-implement reduced setup friction for our internal harness; good balance of opinion and flexibility.
pr-implement fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 25