Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

submit-pr

Étoiles113

Forks2

Mis à jour9 juin 2026 à 08:37

Creates a pull request with a well-structured description after verifying CI passes. Use when the user asks to submit, create, or open a pull request.

Installation

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.

Exécuter dans Manus

Source

MelbourneDeveloper

MelbourneDeveloper/dart_node

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	submit-pr
description	Creates a pull request with a well-structured description after verifying CI passes. Use when the user asks to submit, create, or open a pull request.
disable-model-invocation	true

Submit PR

Create a pull request for the current branch with a well-structured description.

Steps

Run make ci — must pass completely before creating PR
Determine the PR title from git diff main...HEAD
Write PR body using the template in .github/pull_request_template.md
Fill in:
- TLDR: one sentence
- What Was Added: new files, features, deps
- What Was Changed or Deleted: modified behaviour
- How Do The Automated Tests Prove It Works: specific test names or output
- Spec/Doc Changes: if any
- Breaking Changes: yes/no + description
Use gh pr create with the filled template

Rules

Never create a PR if make ci fails
PR description must be specific — no vague placeholders
Only diff against main — ignore commit messages (per CLAUDE.md)
Link to the relevant GitHub issue if one exists

Success criteria

make ci passed
PR created with gh pr create
PR URL returned to user

Plus depuis ce dépôt

même dépôt

build

MelbourneDeveloper/dart_node

Builds all artifacts for this repo. Use when the user asks to build, compile, or produce artifacts, or when verifying that the project compiles cleanly.

2026-06-09113

ci-prep

MelbourneDeveloper/dart_node

Prepares the current branch for CI by running the exact same checks locally, fixing issues at each step. Use before pushing a branch or when the user wants to verify the branch will pass CI.

2026-06-09113

code-dedup

MelbourneDeveloper/dart_node

Searches for duplicate code, duplicate tests, and dead code, then safely merges or removes them. Use when the user says "deduplicate", "find duplicates", "remove dead code", "DRY up", or "code dedup". Requires test coverage — refuses to touch untested code.

2026-06-09113

fix-bug

MelbourneDeveloper/dart_node

Fix a bug using test-driven development. Use when the user reports a bug, describes unexpected behavior, wants to fix a defect, or says something is broken. Enforces a strict test-first workflow where a failing test must be written and verified before any fix is attempted.

2026-06-09113

fmt

MelbourneDeveloper/dart_node

Formats all code in this repo using dart format. Use when the user asks to format code, fix formatting, or before committing changes.

2026-06-09113

lint

MelbourneDeveloper/dart_node

Runs all linters and format checks, then fixes any issues found. Use when the user asks to lint, check code quality, or fix linting errors.

2026-06-09113

name	submit-pr
description	Creates a pull request with a well-structured description after verifying CI passes. Use when the user asks to submit, create, or open a pull request.
disable-model-invocation	true

Submit PR

Create a pull request for the current branch with a well-structured description.

Steps

Run make ci — must pass completely before creating PR
Determine the PR title from git diff main...HEAD
Write PR body using the template in .github/pull_request_template.md
Fill in:
- TLDR: one sentence
- What Was Added: new files, features, deps
- What Was Changed or Deleted: modified behaviour
- How Do The Automated Tests Prove It Works: specific test names or output
- Spec/Doc Changes: if any
- Breaking Changes: yes/no + description
Use gh pr create with the filled template

Rules

Never create a PR if make ci fails
PR description must be specific — no vague placeholders
Only diff against main — ignore commit messages (per CLAUDE.md)
Link to the relevant GitHub issue if one exists

Success criteria

make ci passed
PR created with gh pr create
PR URL returned to user