원클릭으로 Manus에서 모든 스킬 실행

시작하기

burrete-pr-body

스타41

포크3

업데이트2026년 6월 21일 17:28

Prepare or revise a Burrete GitHub pull request title and body from the actual net change.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

SergeiNikolenko

SergeiNikolenko/Burrete

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Burrete PR Body

Use this skill when asked to create or update a PR title/body.

Inputs

Infer the PR from the current branch when possible. If no PR exists, draft the body from the local diff against the intended base branch.

Content Rules

Preserve existing PR body content that the author may not be able to recover, especially images, links, and manually written context.
Explain why the change exists before listing what changed.
Describe the net change, not abandoned intermediate attempts.
Avoid absolute local disk paths.
Avoid confidential information, local device identifiers, signing secrets, tokens, private hostnames, and temporary localhost/session details unless the PR is specifically about that local diagnostic path.
Mention affected surfaces explicitly: desktop app, Quick Look, browser-dev, tokenized preview, iPhone app, plugin/MCP, release, installer, or docs.
Include verification that was actually run. Do not list checks that CI runs automatically unless they were meaningful to this change or newly added.
If docs or release notes need follow-up, include a short section for that.

Suggested Shape

## Why

## What Changed

## Verification

## Notes / Follow-Up

Omit empty sections. Keep the PR body concise and user-facing where the change affects install, launch, preview, update, or agent workflows.

이 저장소의 다른 Skills

같은 저장소

preview-molecular-structures

SergeiNikolenko/Burrete

Preview supported molecular attachments or an explicit public PDB ID in Burrete's interactive viewer, or use the bounded hosted Ketcher editor for transient chemical sketches.

2026-07-1541

external-agent-contract

SergeiNikolenko/Burrete

Use when an external agent must open, observe, control, or render into a Burrete molecular workspace without managing transport details.

2026-07-1541

index

SergeiNikolenko/Burrete

Primary router for Burrete. Use when the plugin is at-mentioned or for molecular workspace work: opening structures, operating Mol* or Ketcher, reviewing SDF/property collections, trajectories, workflow result bundles, molecular reports, or Browser/Computer visual QA.

2026-07-1541

open-workspace

SergeiNikolenko/Burrete

Use when opening molecular artifacts in Burrete Browser preview or desktop app sessions and establishing an observable workspace.

2026-07-1141

visual-qa

SergeiNikolenko/Burrete

Use when visually verifying Burrete Browser preview or desktop app state without replacing typed observe/action contracts.

2026-07-1141

molecular-report

SergeiNikolenko/Burrete

Use when molecular notes, property tables, charts, workflow reports, or provenance should be rendered beside an active Burrete workspace.

2026-07-0941

name	burrete-pr-body
description	Prepare or revise a Burrete GitHub pull request title and body from the actual net change.

Burrete PR Body

Use this skill when asked to create or update a PR title/body.

Inputs

Infer the PR from the current branch when possible. If no PR exists, draft the body from the local diff against the intended base branch.

Content Rules

Preserve existing PR body content that the author may not be able to recover, especially images, links, and manually written context.
Explain why the change exists before listing what changed.
Describe the net change, not abandoned intermediate attempts.
Avoid absolute local disk paths.
Avoid confidential information, local device identifiers, signing secrets, tokens, private hostnames, and temporary localhost/session details unless the PR is specifically about that local diagnostic path.
Mention affected surfaces explicitly: desktop app, Quick Look, browser-dev, tokenized preview, iPhone app, plugin/MCP, release, installer, or docs.
Include verification that was actually run. Do not list checks that CI runs automatically unless they were meaningful to this change or newly added.
If docs or release notes need follow-up, include a short section for that.

Suggested Shape

## Why

## What Changed

## Verification

## Notes / Follow-Up

Omit empty sections. Keep the PR body concise and user-facing where the change affects install, launch, preview, update, or agent workflows.