Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

create-pr

Estrellas8

Forks1

Actualizado1 de julio de 2026 a las 20:32

Automate creation or update of a pull request from the current branch to main, with detailed PR body, task/issue linking, and user prompts for draft/auto-merge. Fallback to commit summary if no task is found.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

dianlight

dianlight/srat

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	create-pr
description	Automate creation or update of a pull request from the current branch to main, with detailed PR body, task/issue linking, and user prompts for draft/auto-merge. Fallback to commit summary if no task is found.

Create or Update Pull Request Skill

Purpose

Automate the process of creating or updating a pull request from the current branch to main in the current repository, following SRAT conventions.

Workflow Steps

Detect Current Branch
- If already on main, abort (cannot PR main → main).
Check for Related Task
- Search for a related task in docs/tasks/ matching the branch name or recent commits.
- If found, extract task details (title, description, checklist, linked issues).
- If not found, summarize recent commit messages for PR body.
Find Issues to Close
- From the related task (if any), collect all open issues that this PR will close.
- Also scan commit messages for Closes #<issue> or similar patterns.
Prompt User
- Ask if the PR should be a draft.
- If not a draft, ask if it should be set to auto-merge.
Verify Remote
- Ensure the current branch is pushed to a remote (origin).
- If not, prompt the user to push before proceeding.
Create or Update PR
- Use mcp_io_github_git_add_comment_to_pending_review to add a comment if updating, or create a new PR if none exists.
- PR body must include:
  - Task details (if any), or commit summary
  - List of issues to close (with GitHub auto-closing syntax)
- Always use main as the base branch.
Post-creation
- If auto-merge requested, enable auto-merge for the PR.

Quality Criteria

PR body is clear, detailed, and references all relevant tasks/issues.
No PR is created from main to main.
User is prompted for draft/auto-merge status.
Fallback to commit summary if no task is found.

Example Prompts

"Create a PR for my current branch"
"Update the PR for this feature branch"
"Open a draft PR for my bugfix branch"

Related Customizations

sync-tasks skill (for task/issue linking)
update-changelog skill (for changelog automation)

Más de este repositorio

mismo repositorio

test-remote-environment

dianlight/srat

Test on the Homeassitant Dev envoronment

2026-07-038

capture-lessons-learned

dianlight/srat

Review the current chat session or recently completed task for reusable implementation or testing lessons, then decide whether to update an existing GitHub instruction and skills, create a new instruction/skill, or store the guidance as repo memory. Use when: finishing a fix, stabilizing a test, capturing a lesson learned, or asking "should we document this for future Copilot sessions?" Triggers on: "lesson learned", "capture lessons learned", "review session for reusable pattern", "update github instruction", "document this fix for future".

2026-07-018

close-task-work

dianlight/srat

Close out a completed docs/tasks/*.md task by validating checklist completion, syncing GitHub issue status/comments, and preparing optional PR summary notes. Triggers on: "close task", "finalize task", "wrap up task 012", "complete docs task".

2026-07-018

create-task

dianlight/srat

Create a new task planning document for SRAT. Use when: adding a feature, planning a fix, documenting a refactor, or creating a new TODO item. Produces a <TaskID>_<Title>.md file in docs/tasks/ using the project task template. Triggers on: "create task", "new task", "add task", "plan feature", "create todo", "new issue task", "document work item".

2026-07-018

homeassistant

dianlight/srat

Expert HomeAssistant development skill for creating custom sensors (template, REST, command line, Python components), building Lovelace dashboards with custom cards and layouts, and developing custom integrations with config flows, coordinators, and multiple platforms. Use this skill when working with HomeAssistant YAML configuration, Python integration development, or dashboard customization.

2026-07-018

implement-task-phase

dianlight/srat

Execute one checklist phase from a docs/tasks/*.md task with strict sequencing: pick exactly one unchecked item, implement only that scope, run targeted validation, and update task progress immediately. Triggers on: "implement next task item", "do task phase", "work on next checklist item", "execute phase 3 of task 012".

2026-07-018

Create or Update Pull Request Skill

Purpose

Automate the process of creating or updating a pull request from the current branch to main in the current repository, following SRAT conventions.

Workflow Steps

Detect Current Branch

If already on main, abort (cannot PR main → main).

Check for Related Task

Search for a related task in docs/tasks/ matching the branch name or recent commits.
If found, extract task details (title, description, checklist, linked issues).
If not found, summarize recent commit messages for PR body.

Find Issues to Close

From the related task (if any), collect all open issues that this PR will close.
Also scan commit messages for Closes #<issue> or similar patterns.

Prompt User

Ask if the PR should be a draft.
If not a draft, ask if it should be set to auto-merge.

Verify Remote

Ensure the current branch is pushed to a remote (origin).
If not, prompt the user to push before proceeding.

Create or Update PR

Use mcp_io_github_git_add_comment_to_pending_review to add a comment if updating, or create a new PR if none exists.
PR body must include:
- Task details (if any), or commit summary
- List of issues to close (with GitHub auto-closing syntax)
Always use main as the base branch.

Post-creation

If auto-merge requested, enable auto-merge for the PR.

Quality Criteria

PR body is clear, detailed, and references all relevant tasks/issues.

No PR is created from main to main.

User is prompted for draft/auto-merge status.

Fallback to commit summary if no task is found.

Example Prompts

"Create a PR for my current branch"

"Update the PR for this feature branch"

"Open a draft PR for my bugfix branch"

Related Customizations

sync-tasks skill (for task/issue linking)

update-changelog skill (for changelog automation)