Menu
Commit, push, and open a draft PR with a written description. Use when ready to share work in progress for review.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Format up an LLM answer into consistent personal markdown style — sentence-case headings and bullet lead-ins, plain dash bullets, no emoji, straight em-dash handling, italics not bold, optional 100-col wrap. Pass a file path to clean in place, or paste raw text to get the cleaned result back in chat.
A decorator on top of /loop with 5-minute timer and autocancel
Action GitHub PR review comments. Provide a PR URL to fix all open comments, or a specific comment URL to fix one.
Review the current branch's diff from a skeptic's perspective before pushing. Optional arg selects the reviewer persona.
Review a GitHub PR. Provide a URL to review without checking it out locally, or omit the URL if the branch is already checked out.
Sync the current branch with the repo's primary branch (main, master, preprod, etc). Pulls primary, switches back, merges in, pushes.
| name | jksubmit |
| description | Commit, push, and open a draft PR with a written description. Use when ready to share work in progress for review. |
Stage any unstaged changes the user intended to include (ask if it's ambiguous), then commit with a message that accurately summarizes the work. Push the branch. Open a draft PR with gh pr create --draft.
Write a PR description that a skeptical senior reviewer would find useful:
If the repo has a PR template, follow its structure. If there's an existing PR for this branch, update its description instead of creating a new one.
Don't ask for confirmation before pushing or creating the PR — the user invoked this because they're ready.
