Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

promote

Estrelas1

Forks0

Atualizado2 de maio de 2026 às 07:46

Promote branch knowledge to project level after merge.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

poyenc

poyenc/agent-plugins

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

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."

Mais deste repositório

mesmo repositório

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."