Skip to content
Back to skills

Pr

ASecurity

Package deliverables + create GitHub PR + sync artifacts

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 1, 2026
ai-agentsgit

Security analysis

A100/100

Scanned October 1, 2026

npx -y skills add sharmapuneet1510/awesome-prompts --skill pr --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pr?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pr
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sharmapuneet1510-awesome-prompts/badge)](https://www.skillsdirectory.com/skills/sharmapuneet1510-awesome-prompts)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pr
description: Package deliverables + create GitHub PR + sync artifacts
disable-model-invocation: true
---

Role and rules: read ${CLAUDE_PLUGIN_ROOT}/reference/agent.md and ${CLAUDE_PLUGIN_ROOT}/reference/rules.md for the sections this function needs.

# orchestrator:pr

**Input:** All generated code + artifacts + context

**Output:**
- GitHub PR created
- Artifacts synced to `.claude/`
- Completion report

**Steps:**
1. Create feature branch
2. Commit each task (5 commits total)
3. Final commit: docs + context artifacts
4. Create PR with detailed description
5. Export agents/skills to `.claude/`
6. Sync task-completion.json
7. Update CLAUDE.md + AGENTS.md
8. Generate completion report

**NEMESIS gate (optional).** Before step 1, if `docs/nemesis/nemesis.yml` exists, is not `enabled: false`, and
`auto_activate.production_release` matches this release, run `orchestrator:nemesis target=<release tag or branch>
trigger=policy` and stop on a `DEFEATED`, `CHALLENGED` or `INSUFFICIENT EVIDENCE` verdict; on `SURVIVED WITH
CONDITIONS`, put its conditions in the PR description. After two consecutive blocking
results (`DEFEATED`, `CHALLENGED` or `INSUFFICIENT EVIDENCE`) for the same release (count the reports in
`docs/nemesis/` whose `change` header matches it), stop and hand the decision to a human. Skip this when the file is absent, and
when you are yourself running as a NEMESIS challenger.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…