ワンクリックでManusで任意のスキルを実行

始める

promote

スター1

フォーク0

更新日2026年5月2日 07:46

Promote branch knowledge to project level after merge.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

poyenc

poyenc/agent-plugins

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

/promote [branch]

Promote branch knowledge to project level.

Arguments

[branch]: optional branch name. If omitted, auto-detects merged branches.

Steps

If [branch] is provided:
- Resolve the branch directory (sanitize name, find in branches/).
- Proceed to step 3.
If no argument:
- Run ${CLAUDE_PLUGIN_ROOT}/scripts/detect-merged.sh --project-dir <project-dir> --target-branch <default-branch> to find merged branches.
- If none found: "No merged branches with unpromoted knowledge."
- If multiple found: list them and process each.
For each branch to promote: a. Read all knowledge/ and workflows/ topic files from the branch overlay. b. For each finding, classify:
- Promote (general): architectural patterns, hardware behavior, debugging techniques, performance patterns, API insights, conventions
- Archive (branch-specific): branch commit hashes, WIP status, temporary workarounds, task configs, unverified hypotheses c. For promotable content:
- If a matching project-level topic exists → append to it
- If no matching topic → create new topic file, add to project index.md
- After appending, if the topic file exceeds maintenance.topic-max-lines (from directives.md), split ### subsections into sibling topic files and update the project index.md. d. Move branches/<sanitized>/ to archive/<sanitized>/ e. Update archive meta.md with **Status:** promoted and date f. Report: "Promoted findings from '' to project level. Branch archived."

このリポジトリの他の Skills

同じリポジトリ

recall-reorg

poyenc/agent-plugins

Re-organize recall knowledge/workflow topics into their best shape — unify topic filenames, frontmatter, and titles, merge overlapping topics, compact stale content, extract shared general principles into their own topics, and rewrite the index coherently. Use whenever the user says "re-org the recall topics", "clean up recall", "make the recall coherent", "extract a general topic", "tidy the knowledge index", or when recall files have drifted (mismatched names, duplicated content, oversized files, a stale index). Keeps recall well-managed as a whole rather than fixing one file at a time.

2026-07-171

branch-status

poyenc/agent-plugins

Overview of all tracked branches (active, stale, merged, archived).

2026-05-021

recall-init

poyenc/agent-plugins

One-time project setup — creates directories, config, and initial files.

2026-05-021

recall-status

poyenc/agent-plugins

Show recall state — branch, task, loaded topics, stale/unpromoted info.

2026-05-021

recall-add

poyenc/agent-plugins

Add knowledge entry with scope control (--project/--branch flags).

2026-04-241

recall-search

poyenc/agent-plugins

Search across all knowledge files including archives.

2026-04-241

name	promote
description	Promote branch knowledge to project level after merge.

/promote [branch]

Promote branch knowledge to project level.

Arguments

[branch]: optional branch name. If omitted, auto-detects merged branches.

Steps

If [branch] is provided:
- Resolve the branch directory (sanitize name, find in branches/).
- Proceed to step 3.
If no argument:
- Run ${CLAUDE_PLUGIN_ROOT}/scripts/detect-merged.sh --project-dir <project-dir> --target-branch <default-branch> to find merged branches.
- If none found: "No merged branches with unpromoted knowledge."
- If multiple found: list them and process each.
For each branch to promote: a. Read all knowledge/ and workflows/ topic files from the branch overlay. b. For each finding, classify:
- Promote (general): architectural patterns, hardware behavior, debugging techniques, performance patterns, API insights, conventions
- Archive (branch-specific): branch commit hashes, WIP status, temporary workarounds, task configs, unverified hypotheses c. For promotable content:
- If a matching project-level topic exists → append to it
- If no matching topic → create new topic file, add to project index.md
- After appending, if the topic file exceeds maintenance.topic-max-lines (from directives.md), split ### subsections into sibling topic files and update the project index.md. d. Move branches/<sanitized>/ to archive/<sanitized>/ e. Update archive meta.md with **Status:** promoted and date f. Report: "Promoted findings from '' to project level. Branch archived."