reductstore/create-pr
.codex/skills/create-pr/SKILL.md
Create GitHub pull requests with the gh CLI using the reductstore/.github PR template, then update CHANGELOG.md with the created PR ID and commit the changelog (do not push). Use when a user asks to open a PR and record its ID in the changelog.
$ install --global
skillsauthnpx skillsauth add reductstore/reductstore create-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 11, 2026, 10:37 PM50.9s2 files scanned
SKILL.md
- name:
- create-pr
- description:
- Create GitHub pull requests with the gh CLI using the reductstore/.github PR template, then update CHANGELOG.md with the created PR ID and commit the changelog (do not push). Use when a user asks to open a PR and record its ID in the changelog.
Create Pr
Overview
Create a PR using the standardized template from reductstore/.github, then record the PR number in CHANGELOG.md and commit the changelog without pushing.
Workflow
1) Preconditions
- Ensure
gh auth statusis logged in and the current branch is the intended PR branch. - Ensure the working tree is clean (or only the intended changes are present).
- Use context from the current conversation to infer intent, scope, and any constraints.
2) Understand changes and rationale
- Compare the current branch against
mainto understand what changed and why (use this to derive the PR title, description, and rationale):git fetch origin maingit log --oneline origin/main..HEADgit diff --stat origin/main...HEADgit diff origin/main...HEAD
- If the branch name starts with an issue number (e.g.,
123-...), use that issue in the rationale and fill theCloses #line in the PR template. - If the branch name does not include an issue number, infer the likely issue from changes and conversation context, or leave
Closes #empty if unsure.
3) Fetch the PR template
Use the helper script to download the latest PR template from reductstore/.github:
./.codex/skills/create-pr/scripts/fetch_pr_template.sh /tmp/pr_template.md
Fill in the template file with the relevant summary, testing, and rationale derived from the diff and conversation context.
4) Create the PR with gh
Use the filled template as the PR body:
gh pr create --title "<title>" --body-file /tmp/pr_template.md
Capture the PR number after creation:
gh pr view --json number -q .number
5) Update CHANGELOG.md
- Find the appropriate section (usually the most recent/unreleased section).
- Add a new entry following the existing style in the file.
- Include the PR ID as
#<number>exactly as prior entries do.
6) Commit (no push)
Stage and commit the changelog update only:
git add CHANGELOG.md
git commit -m "Update changelog for PR #<number>"
Do not push.
Resources
scripts/
fetch_pr_template.sh: Download the latest PR template from reductstore/.github.
Related Skills
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026
steipete/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,588SKILL.mdUpdated Apr 13, 2026
steipete/xurl
tools
VerifiedTrustedCommunity
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.
356,423SKILL.mdUpdated Apr 13, 2026