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

$pwd:

branch-name

Name: Branch Name
Author: makeplane

// Use when starting a new branch or renaming an existing one — produces a branch name in the format `<type>/<work-item-id>-<short-description>` that's compatible with the create-pr skill's work item ID extraction.

Manus에서 실행

$ git log --oneline --stat

stars:49,961

forks:4,365

updated:2026년 5월 26일 16:55

SKILL.md

readonly

name	branch-name
description	Use when starting a new branch or renaming an existing one — produces a branch name in the format `<type>/<work-item-id>-<short-description>` that's compatible with the create-pr skill's work item ID extraction.
user_invocable	true

Branch Naming

Create branch names that follow the convention <type>/<work-item-id>-<short-description>, where the work item ID can be cleanly extracted later (e.g., by the create-pr skill).

Format

<type>/<work-item-id>-<short-description>

All lowercase, hyphen-separated
Work item ID stays in its original form but lowercased (e.g., SILO-1146 → silo-1146)
Short description is 2–5 words in kebab-case, focused on the what, not the how

Workflow

Determine the type based on the work being done:
- feat — new functionality
- fix — bug fix
- chore — tooling, deps, config, non-user-facing housekeeping
- refactor — restructuring without behavior change
- docs — documentation only
- perf — performance improvement
Determine the work item ID:
- If the user gives one, use it
- If they reference a Plane work item (e.g., a URL or title), extract the ID
- If none exists, ask the user — don't invent one
Write the short description:
- 2–5 words in kebab-case
- Describe the outcome, not the implementation (add-app-tile-visibility, not update-tile-component)
- Skip filler words (the, a, for)
Assemble and create the branch:

   git checkout -b <type>/<work-item-id-lowercased>-<short-description>

Return the branch name to the user.

Examples

fix/silo-1146-relative-config-urls
feat/web-1234-app-tile-visibility
chore/web-2201-bump-eslint
refactor/silo-980-extract-auth-middleware
docs/web-1500-pr-template-update
perf/silo-1310-cache-workspace-lookup

Common Mistakes

Putting the work item ID at the end instead of after the type (breaks extraction)
Using underscores or camelCase instead of hyphens
Uppercasing the work item ID inside the branch name (it should be lowercase here, uppercased only when used as the PR title prefix)
Writing a long, narrative description — keep it scannable
Omitting the work item ID when one exists in Plane
Using a type that won't match the eventual PR type (pick the type you'd use in the PR title)

related-skills.json

같은 저장소

create-pull-request.md

from "makeplane/plane"

Use when creating a pull request for the current branch — gathers branch context, generates a PR description following the repo's pull_request_template.md, and creates the PR with a Plane work item ID prefix in the title.

2026-05-2650.0k

release-notes.md

from "makeplane/plane"

Generate release notes for a Plane release PR in either `makeplane/plane-cloud` (date-based versioning, e.g. `release: vYY.MM.DD-N`) or `makeplane/plane-ee` (semver, e.g. `release: vX.Y.Z`). Reads PR commits, filters out noise, categorizes by conventional-commit type, optionally enriches via Plane MCP, and writes the result as the PR description in the GitHub Releases format.

2026-05-2650.0k

translate.md

from "makeplane/plane"

Translate or update keys in packages/i18n/src/locales. Use whenever adding, changing, or reviewing strings across any target locale — enforces do-not-translate terminology, CLDR plural forms, placeholder/tag preservation, per-locale punctuation/register, and the AI-translation review workflow. Required reading before touching any *.json under src/locales.

2026-05-2650.0k

package.json

"author": "makeplane"

"repository": "makeplane/plane"

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

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

소프트웨어 개발자컴퓨터 및 수학직15-1252L4

Branch Naming

Create branch names that follow the convention <type>/<work-item-id>-<short-description>, where the work item ID can be cleanly extracted later (e.g., by the create-pr skill).

Format

<type>/<work-item-id>-<short-description>

All lowercase, hyphen-separated

Work item ID stays in its original form but lowercased (e.g., SILO-1146 → silo-1146)

Short description is 2–5 words in kebab-case, focused on the what, not the how

Workflow

Determine the type based on the work being done:

feat — new functionality
fix — bug fix
chore — tooling, deps, config, non-user-facing housekeeping
refactor — restructuring without behavior change
docs — documentation only
perf — performance improvement

Determine the work item ID:

If the user gives one, use it
If they reference a Plane work item (e.g., a URL or title), extract the ID
If none exists, ask the user — don't invent one

Write the short description:

2–5 words in kebab-case
Describe the outcome, not the implementation (add-app-tile-visibility, not update-tile-component)
Skip filler words (the, a, for)

Assemble and create the branch:

git checkout -b <type>/<work-item-id-lowercased>-<short-description>

Return the branch name to the user.

Examples

fix/silo-1146-relative-config-urls feat/web-1234-app-tile-visibility chore/web-2201-bump-eslint refactor/silo-980-extract-auth-middleware docs/web-1500-pr-template-update perf/silo-1310-cache-workspace-lookup

Common Mistakes

Putting the work item ID at the end instead of after the type (breaks extraction)

Using underscores or camelCase instead of hyphens

Uppercasing the work item ID inside the branch name (it should be lowercase here, uppercased only when used as the PR title prefix)

Writing a long, narrative description — keep it scannable

Omitting the work item ID when one exists in Plane

Using a type that won't match the eventual PR type (pick the type you'd use in the PR title)

branch-name

Branch Naming

Format

Workflow

Examples

Common Mistakes

이 저장소의 다른 Skills

이 저장소의 다른 Skills

Branch Naming

Format

Workflow

Examples

Common Mistakes