create-pr
Create a GitHub pull request from staged task changes or an already-committed current branch. Deliver source/config/ reference changes together with their computed source-owned `bin_artifacts` closure. PR validation routing is owned by the default-branch trusted workflow; snapshots, gamedata, and ma
v2026.11.13-dcf20203 instalaciones+3 en 7 días67 EstrellasMITsincronizado hace 12 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install hlnd2t/create-prEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paqueted94304d3…6ff27da3
d94304d35e28…db426ff27da32 archivos · 3.5 KBEscaneoBajosin hallazgos
Fuentegithub.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/create-pr@dcf2020
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
Create one pull request using exactly one delivery mode:
staged-delivery— commit the caller's explicitly staged source-owned change set, push adev*branch, and create the PR.committed-branch— push an existing clean non-mainbranch that is ahead oforigin/main, without rewriting or supplementing its commits.
Both modes preserve the captured source-owned change set. The PR workflow independently selects its validation path after the PR exists; this skill neither predicts nor influences that routing.
Inputs
gamever— optional descriptive value for the PR body. Never resolve or require it for local delivery.branch— optionaldev*branch name forstaged-delivery. If omitted onmain, derivedev-<topic>from the staged change. Ignore it incommitted-branch.commit_title— optional Conventional Commit title forstaged-delivery.pr_title/pr_body— optional PR text. Otherwise derive truthful text from the delivered diff and caller-supplied test results.issue— optional issue number. AddCloses #<issue>to the PR body.
Safety Rules
- Run from the repository root and require an
originremote plus successfulgh auth status. - Never commit directly to
main, force-push, amend existing commits, or usegit add -A/git add .. - Preserve unrelated untracked files and never stage them.
- Require zero unstaged tracked changes at invocation. This forbids partially staged paths and unrelated work.
- In
staged-delivery, the initial staged path list is the immutable authorized change set. It must include every affected/downstream canonical artifact underbin_artifacts/that belongs to the source/config/reference change. - Reject tracked
gamesymbols/**,gamedata/**,release-manifests/**, andbin/**/*.yaml; these are forbidden legacy or Release-derived namespaces, not PR deliverables. - In
committed-branch, require an empty index, a non-mainattached branch, at least one commit ahead oforigin/main, and a non-emptyorigin/main...HEADdiff. Never create a supplemental publication commit. - PR validation routing, including whether isolated rebuild and C++ validation run, belongs only to the trusted default-branch workflow after the PR exists. Do not classify or predict its validation path locally.
- Snapshot/gamedata publication runs only in the release pipeline. Never claim workflow-owned CI gates passed locally.
- Commit and push commands may take longer than an interactive timeout. Wait for their real exit status; do not infer success from elapsed time.
Step 1: Select and Guard the Delivery Mode
Record the current state and fetch the target branch:
git branch --show-current
git status --short
git diff --cached --quiet
git diff --cached --name-only
git diff --cached --name-status
git diff --cached --stat
git diff --name-only
git ls-files --others --exclude-standard
git remote
gh auth status
git fetch origin main --prune
git rev-parse HEAD
git rev-parse origin/main
git rev-list --count origin/main..HEAD
git diff --name-only origin/main...HEAD
git diff --name-status origin/main...HEAD
git diff --stat origin/main...HEADOn Windows PowerShell, use explicit argument arrays and capture $LASTEXITCODE for native commands. Do not use the
automatic $args variable as a named parameter:
function Run-Native {
param(
[Parameter(Mandatory)][string]$Name,
[Parameter(Mandatory)][string]$Executable,
[Parameter(Mandatory)][string[]]$CommandArgs
)
$output = & $Executable @CommandArgs 2>&1
$exitCode = $LASTEXITCODE
Write-Output "<<<$Name exit=$exitCode>>>"
if ($null -ne $output) { $output | ForEach-Object { $_.ToString() } }
Write-Output "<<<END $Name>>>"
}git diff --name-only must be empty in both modes. Untracked files may remain, but record and preserve them.
Mode A — staged-delivery
Exit 1 from git diff --cached --quiet proves staged changes exist. Save the exact cached path list as
INITIAL_STAGED_PATHS, review the cached diff for unrelated files or credentials, and derive the summary.
- On
main, validate the supplied/derived branch withgit check-ref-format --branch <dev-branch>and require it not to exist locally or onorigin. - On an existing
dev*branch whoseHEADequalsorigin/main, use that branch. - On any other branch, stop and ask the caller to use
mainor a suitabledev*branch.
Mode B — committed-branch
Exit 0 means the index is empty. Require an attached branch other than main, a valid branch name, an ahead count
greater than zero, a non-empty origin/main...HEAD diff, and a clean tracked worktree. Capture INITIAL_BRANCH,
INITIAL_HEAD, AHEAD_COUNT, and INITIAL_COMMITTED_PATHS. Read the full diff and log; never rewrite those commits.
For either mode, set PR_BRANCH, then reject duplicate open PRs:
gh pr list --state open --head <PR_BRANCH> --json urlStep 2: Revalidate the Authorized Index
Do not run formatters or generators in this skill. In staged-delivery, verify that the cached path list still equals
INITIAL_STAGED_PATHS and that no unstaged tracked path exists:
git diff --name-only
git diff --cached --quiet
git diff --cached --name-only
git diff --cached --stat
git diff --cached --checkRequire a non-empty staged diff, review it again, and stage nothing else. Explicitly reject any forbidden legacy/output
namespace listed in the Safety Rules. In committed-branch, apply the same path rejection to origin/main...HEAD, then require both index and
tracked worktree to remain clean and HEAD == INITIAL_HEAD.
Step 3: Create the Source Commit
In staged-delivery, create the validated branch when currently on main:
git switch -c <dev-branch>Derive or validate <type>(scope): <summary>: begin with a verb, keep it at most 100 characters, and omit the final
period. Commit exactly the existing staged index:
git commit -m "<commit_title>" -m "Co-Authored-By: Codex <[email protected]>"Verify the commit changed exactly INITIAL_STAGED_PATHS and the tracked worktree/index are clean. In
committed-branch, create no commit and require HEAD == INITIAL_HEAD.
Step 4: Push and Create the Pull Request
Immediately before push, require the intended branch, clean index/worktree, a positive ahead count, and a final
origin/main...HEAD path list equal to the captured source paths. In committed-branch, also require
HEAD == INITIAL_HEAD.
Push without force:
git push -u origin <PR_BRANCH>Build a truthful body from the delivered diff and caller-supplied validation evidence. Do not predict the workflow's validation path or claim its gates have already passed. A suitable shape is:
## Summary
- <behavioral change>
- <supporting change>
## Validation
- implementation-specific tests: <commands/results supplied by the caller>
- repository PR validation: delegated to trusted `source-artifact-required` / `pr-validate` CI
Closes #<issue>If gamever was supplied, it may be included as descriptive context, not as evidence of local validation. Omit the
issue line when absent.
Create exactly one PR against main:
gh pr create --base main --head <PR_BRANCH> --title "<pr_title>" --body "<pr_body>"Report the branch, commit SHA, pushed remote, PR URL, and final committed paths. For committed-branch, report
INITIAL_HEAD and the initial ahead count. If push succeeds but PR creation fails, report the remote branch and exact
failure; do not delete the branch or create another commit.
Checklist
- Exactly one delivery mode was selected and no unstaged tracked changes existed.
- The local commit contains the source/config/reference change and complete
bin_artifactsclosure. - No tracked snapshot, gamedata, release-manifest, or
bin/**/*.yamlpath was added. - The PR body does not predict the workflow-owned validation path or claim unrun CI results.
- No duplicate PR existed; the branch was pushed without force; exactly one PR was opened against
main.
Archivos de esta versión
agents/1277 B
- openai.yaml277 B
- SKILL.md8.4 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.11.13-dcf2020 | 13 nov 2026 | dcf2020 | d94304d3 | Firmada | – |
Más de HLND2T
Todo de este publicadorMás en Informes y cumplimiento
Ver la categoría- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login