New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prcdx

by n0an in n0an/VivaDicta

Create a GitHub Pull Request in Codex with Claude and Codex review requests and standard GitHub polling

MITAuto-check passedMobile

Install Prcdx

skills CLI
$ npx skills add n0an/VivaDicta --skill prcdx -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install n0an/VivaDicta prcdx --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/n0an/VivaDicta.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prcdx .claude/skills/prcdx && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prcdx
GitHub stars
131
Token cost
~1.4k tokens
SKILL.md length
743 words
Files
2
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Create a GitHub Pull Request in Codex with Claude and Codex review requests and standard GitHub polling

  • Works in 6 steps: First, check the current git status and… → If there are uncommitted changes, ask if… → Ensure the current branch is not main or… → …
  • Mobile work in your project
  • SKILL.md covers Task: Create a GitHub Pull…, IMPORTANT: Final Summary, Review Flow and Suggested Polling Approach, plus 4 more sections
  • Calls gh; reaches github.com

What it does

Prcdx is an agent skill from n0an/VivaDicta. Create a GitHub Pull Request in Codex with Claude and Codex review requests and standard GitHub polling

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Mobile. It works with GitHub. The repository describes itself as: iOS & watchOS speech-to-text app with AI voice keyboard, on-device RAG, and chat with your notes - powered by Apple Foundation Models, WhisperKit, NVIDIA Parakeet, and 20+ AI…. The licence is MIT.

When your agent uses it

  • Mobile work in your project

Example prompts

  • “/prcdx”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. First, check the current git status and uncommitted changes.
  2. If there are uncommitted changes, ask if they should be committed first.
  3. Ensure the current branch is not main or master.
  4. Push the current branch to remote if needed.
  5. Create the pull request using gh pr create with
  6. Return the PR URL when complete.

What it can do on your machine

Read from SKILL.md and the folder at commit b141304. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prcdx loads about 1.4k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 743 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~27
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from n0an/VivaDicta at commit b141304, republished under its MIT licence (© n0an). 743 words, ~1,366 tokens.

Download SKILL.mdSave it as .claude/skills/prcdx/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
prcdx
description
Create a GitHub Pull Request in Codex with Claude and Codex review requests and standard GitHub polling
disable-model-invocation
true

prcdx

You are given the following context: $ARGUMENTS

Task: Create a GitHub Pull Request in Codex

Based on the provided context, create a pull request following these steps:

  1. First, check the current git status and uncommitted changes.
  2. If there are uncommitted changes, ask if they should be committed first.
  3. Ensure the current branch is not main or master.
  4. Push the current branch to remote if needed.
  5. Create the pull request using gh pr create with:
    • A clear, descriptive title
    • A comprehensive description including:
      • Summary of changes
      • Testing performed
      • Any breaking changes or notes
  6. Return the PR URL when complete.

IMPORTANT: Final Summary

ALWAYS end your response with a clear summary that includes:

  • What was done (branch created, commits made, PR opened, review requested, etc.)
  • The PR URL (for example: PR #123: https://github.com/owner/repo/pull/123)
  • Whether Claude review was requested
  • Whether Codex review was requested
  • Whether the PR is ready for review

Format the PR link prominently so it's easy to find.

If no arguments are provided, create a PR with an auto-generated title and description based on the current branch and commit history.

Use --draft if the work is clearly in progress.

Review Flow

After the PR is created, follow this review workflow unless the user explicitly says not to:

  1. Post a comment requesting Claude review:
    bash
    gh pr comment <PR_NUMBER> --body "@claude please review this PR"
  2. Post a second comment requesting Codex review:
    bash
    gh pr comment <PR_NUMBER> --body "@codex please review this PR"
  3. Poll GitHub using standard CLI or API commands, not Claude Code slash commands.
  4. Check issue comments, PR reviews, and inline review comments every 2 minutes for a bounded period.
  5. Codex review usually takes longer than Claude review. Do not stop polling just because Claude replied first.
  6. Continue polling until you see a real Codex comment or review, not just an "in progress" placeholder, or until a reasonable bounded wait expires.
  7. Show the returned review feedback to the user and ask what they want to do next. If Claude replied but Codex has not yet replied, say that Codex review is still pending and keep polling until the bounded wait is reached.

Suggested Polling Approach

Use normal GitHub commands such as:

bash
gh pr view <PR_NUMBER> --json comments,reviews,url

or:

bash
gh api repos/<owner>/<repo>/issues/<PR_NUMBER>/comments
gh api repos/<owner>/<repo>/pulls/<PR_NUMBER>/reviews

When polling:

  • Record a baseline timestamp immediately before or after posting the @claude and @codex comments
  • Only treat newer comments or reviews as candidate review results
  • Ignore empty bodies and obvious "review in progress" placeholders
  • Codex review usually takes longer, so keep checking until you see Codex feedback or the bounded wait expires
  • Stop after a reasonable bounded wait if no review arrives, and tell the user that Claude review and Codex review were requested but have not yet returned
Show full SKILL.md (308 more words)Show less

IMPORTANT: Review Inspection Hygiene

Do not assume a top-level review with generic text means there are no findings.

  • Always inspect inline review comments / file-level review threads in addition to issue comments and top-level reviews.
  • Actionable feedback can exist only in inline comments even when the main review body looks boilerplate.
  • Inline comments may be attached to an older reviewed commit on the same branch and still be relevant.
  • Before dismissing a review as empty, check all three surfaces:
    • issue comments
    • PR reviews
    • pull request review comments / inline comments

Suggested extra command:

bash
gh api repos/<owner>/<repo>/pulls/<PR_NUMBER>/comments

Handling Review Feedback

  • Real critical bugs (regressions, data loss, crashes, security issues): fix them immediately without asking.
  • Everything else (style, theoretical issues, nice-to-haves, non-critical improvements): present to the user with your assessment and ask before fixing.

Merge Requests

If the user explicitly says merge, do not wait for CI to finish.

  • Merge the PR immediately using a regular merge commit.
  • Do not block on pending checks unless the user explicitly asks to wait.
  • If you see ongoing GitHub Actions build jobs for that PR or branch, submit a cancel request after merging instead of leaving them running.
  • Do not wait for GitHub to confirm the cancellation. One cancel request is enough unless the user explicitly asks you to verify.
  • Right after the merge, switch the local repository back to main.

Post-Merge: Update What's New

After the PR is merged, update the running What's New file in the Obsidian vault:

  • File: Projects/VivaDicta/what's new/whats-new-running.md in the vault at /Users/antonnovoselov/Documents/Vault/
  • Skip if the PR is a one-liner simple fix, bug fix, refactor, or minor cleanup that users wouldn't notice.
  • Add a concise, user-facing bullet point when the PR introduces a new feature or notable improvement. Write it from the user's perspective (what they can now do), not technical details. This file feeds into App Store Connect "What's New" release notes.

© n0an, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/prcdx of n0an/VivaDicta.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit b141304

Compare with similar skills

Prcdx next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prcdx compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prcdx this skilln0an/VivaDicta131—~1.4kAutomated safety check: PassMIT
Maa Issue Log AnalysisMaaAssistantArknights/MaaAssistantArknights24k—~4kAutomated safety check: PassAGPL-3.0
Workbuddy Skin Studiocdredfox/workbuddy-skin-studio196—~1.5kAutomated safety check: PassMIT
Fix CrashMartinStyk/apk-analyzer369—~2.5kAutomated safety check: PassGPL-3.0
Frb PR Chain Splitfzyzcjy/flutter_rust_bridge5.4k—~1.9kAutomated safety check: PassMIT
TriageK9i-0/ccpocket1.1k—~334Automated safety check: PassMIT

Similar skills

  • Maa Issue Log Analysis

    MaaAssistantArknights/MaaAssistantArknights

    分析 MaaAssistantArknights 上游仓库公开 Issue（https://github.com/MaaAssistantArknights/MaaAssistantArknights/issues/...

    24k GitHub stars~4k tokensUpdated yesterday
    MobileAuto-check passed

  • Workbuddy Skin Studio

    cdredfox/workbuddy-skin-studio

    Apply a reversible theme/skin to the WorkBuddy desktop app (Tencent AI office agent) via local Chromium DevTools Protocol (CDP) injection.

    196 GitHub stars~1.5k tokensUpdated 2 mo ago
    MobileAuto-check passed

  • Fix Crash

    MartinStyk/apk-analyzer

    A skill your agent uses to fix a specific production crash or non-fatal — pulling its Crashlytics data, finding the linked GitHub issue, root-causing it, reproducing it, fixing it, and verifying the…

    369 GitHub stars~2.5k tokensUpdated 3 days ago
    MobileAuto-check passed

  • Frb PR Chain Split

    fzyzcjy/flutter_rust_bridge

    A skill your agent uses when an FRB PR contains independently landable work that should be extracted into predecessor PRs and connected as a GitHub PR chain without wasting full automatic CI.

    5.4k GitHub stars~1.9k tokensUpdated yesterday
    MobileAuto-check passed

  • Triage

    K9i-0/ccpocket

    GitHub Issueの対応判断と、PRの調査・手直し・検証・マージを行う。PR指定時は取り込みまで進めるのが既定. An agent skill from K9i-0/ccpocket.

    1.1k GitHub stars~334 tokensUpdated 5 days ago
    MobileAuto-check passed

  • Release Asc CLI

    rorkai/App-Store-Connect-CLI

    Publish and verify a new release of the App-Store-Connect-CLI repository.

    7.7k GitHub stars~2.4k tokensUpdated today
    MobileAuto-check passed

More from n0an/VivaDicta

All 20 skills in this repo

  • Swiftdata Pro

    n0an/VivaDicta

    Writes, reviews, and improves SwiftData code using modern APIs and best practices.

    131 GitHub starsUsed in 1 repo~930 tokens
    Auto-check passed

  • iOS Simulator Skill

    n0an/VivaDicta

    21 production-ready scripts for iOS app testing, building, and automation.

    131 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Asc Metadata Sync

    n0an/VivaDicta

    Sync and validate App Store metadata and localizations with asc, including legacy metadata format migration.

    131 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

  • Asc Aso Rankings

    n0an/VivaDicta

    Pull current keyword rankings from Astro MCP, compare against the previous rankings check, and save a new rankings file to the vault.

    131 GitHub stars~985 tokensUpdated 3 days ago
    Auto-check passed

  • Coverage Report

    n0an/VivaDicta

    Measure VivaDicta test code coverage from the terminal. An agent skill from n0an/VivaDicta.

    131 GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

  • Loc Report

    n0an/VivaDicta

    Count Swift lines of code across the VivaDicta codebase and refresh the production-vs-test history chart.

    131 GitHub stars~825 tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Prcdx

What does Prcdx do?

Create a GitHub Pull Request in Codex with Claude and Codex review requests and standard GitHub polling. Prcdx is an agent skill from n0an/VivaDicta.

When should I use Prcdx?

Prcdx fits situations like: mobile work in your project.

How do I install Prcdx in Claude Code?

Run `npx skills add n0an/VivaDicta --skill prcdx -a claude-code`. Or copy the skill folder (.agents/skills/prcdx in n0an/VivaDicta) into .claude/skills/prcdx in your project. Claude Code loads it when a task matches its description.

How do I install Prcdx in Codex?

Run `npx skills add n0an/VivaDicta --skill prcdx -a codex`. Or copy the skill folder (.agents/skills/prcdx in n0an/VivaDicta) into .agents/skills/prcdx in your project. Codex loads it when a task matches its description.

Can I use Prcdx in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add n0an/VivaDicta --skill prcdx -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prcdx, .gemini/skills/prcdx, .github/skills/prcdx and .opencode/skills/prcdx in your project.

What does Prcdx need to run?

Going by SKILL.md and its folder, Prcdx needs the command-line tools its instructions call (gh).

Does Prcdx access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Prcdx safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prcdx use?

Prcdx is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prcdx use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prcdx?

Skills that share tags, products or a category with Prcdx: Maa Issue Log Analysis (MaaAssistantArknights/MaaAssistantArknights, 24k stars), Workbuddy Skin Studio (cdredfox/workbuddy-skin-studio, 196 stars), Fix Crash (MartinStyk/apk-analyzer, 369 stars) and Frb PR Chain Split (fzyzcjy/flutter_rust_bridge, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prcdx?

n0an (a GitHub user) maintains it in n0an/VivaDicta, which has 131 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 5, 2026.

Source: n0an/VivaDicta on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.