Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

push

Sterne1.283

Forks1.262

Aktualisiert4. Juni 2026 um 12:55

Push the current branch in strapi/documentation to origin. Validates branch name against git-rules.md conventions.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

strapi

strapi/documentation

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	push
description	Push the current branch in strapi/documentation to origin. Validates branch name against git-rules.md conventions.
argument-hint	(no arguments)
user-invocable	true

Documentation Push

Scope: designed for strapi/documentation (and its forks).

Step 1: Apply shared push rules

Read and follow ../_shared/push-rules.md for: gathering state, safety checks, upstream status, showing the plan, and executing the push.

Step 2: Branch name validation (extra, doc-specific)

Check the branch name follows git-rules.md conventions:

Must start with /cms/, /cloud/, or /repo/
No other prefixes (/doc/, /docs/, /feat/, /fix/, etc.)

If non-compliant, warn the user but do not block (renaming an existing branch is disruptive). Suggest the correct prefix for future reference.

Step 3: Suggest branch creation if on main

If on main, analyze recent changes to detect the area (cms/cloud/repo), then suggest:

Suggested: git checkout -b /<prefix>/<description>

Mehr aus diesem Repository

gleiches Repository

review

strapi/documentation

Top-level review orchestrator: runs style-check, outline-check, outline-ux-analyzer, code-verify, coherence-check, and pitfalls-check on a file, directory, or PR.

2026-06-301.3k

strapi/documentation

Create a pull request on strapi/documentation following git-rules.md. Strict flat-text description, no headings, no test plan.

2026-06-181.3k

document

strapi/documentation

End-to-end documentation orchestrator: chains all four inki phases (research, write, review, submit) for a single subject. Gates between each phase by default; --non-interactive chains without pauses and runs a review-fix loop. The simplest way to document a subject from scratch.

2026-06-171.3k

outline

strapi/documentation

Generate an outline for a new documentation page from a topic brief and the appropriate template.

2026-06-161.3k

pitfalls-add

strapi/documentation

Add a new entry to the known-pitfalls catalog that pitfalls-check audits against. Verifies the correct pattern against the Strapi source before adding, and confirms with the user. Use when you have found a documentation mistake worth catching automatically in future reviews.

2026-06-161.3k

pr-fix

strapi/documentation

Rewrite the title or description/body of one or more open PRs on strapi/documentation to match git-rules.md. Strict one-by-one confirmation, or auto-edit with --non-interactive.

2026-06-161.3k

name	push
description	Push the current branch in strapi/documentation to origin. Validates branch name against git-rules.md conventions.
argument-hint	(no arguments)
user-invocable	true

Documentation Push

Scope: designed for strapi/documentation (and its forks).

Step 1: Apply shared push rules

Read and follow ../_shared/push-rules.md for: gathering state, safety checks, upstream status, showing the plan, and executing the push.

Step 2: Branch name validation (extra, doc-specific)

Check the branch name follows git-rules.md conventions:

Must start with /cms/, /cloud/, or /repo/
No other prefixes (/doc/, /docs/, /feat/, /fix/, etc.)

If non-compliant, warn the user but do not block (renaming an existing branch is disruptive). Suggest the correct prefix for future reference.

Step 3: Suggest branch creation if on main

If on main, analyze recent changes to detect the area (cms/cloud/repo), then suggest:

Suggested: git checkout -b /<prefix>/<description>