recursive-spine-pollinate
仓库创建 2026年7月7日最近提交 3 天前SkillHot 收录 15 小时前
▸ 精选理由
便于在多个仓库间复用已验证实践,适合多仓库团队。
▸ 风险提示
会在仓库内写入文件并创建/修改 issue,可能改动代码库
这个 Skill 做什么
捕获或在仓库间拉取“已验证”代码/配置片段并记录为 pollen 注册条目。
把在真实工作中被验证有效的代码或配置片段打包成 pollen(注册条目)并记录到 hive,或者从各个 hive 拉出适合当前仓库的移植并把变更回写到记录。用在发现可复用的解决方案想跨项目推广时。流程强调可追溯的记录、配对 issue 跟踪,并把私有证明只放到私有 hive。
▸ 展开 SKILL.md 英文原文
Use when something just proved itself in real work and should be carried to other projects — captures it as a pollen record in the builder's hive (registry file + paired issue), or, in pull mode, reads every configured hive and offers relevant transplants into the current repo, recording each transplant back onto the record. Interview-driven hive config; never ships a default hive; routes private-proof pollen to a private hive only.
1
Stars
0
Forks
8
仓库内 Skill
积累中
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/slopstopper/recursive-spine/main/skills/recursive-spine-pollinate/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/slopstopper/recursive-spine/main/skills/recursive-spine-pollinate/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# recursive-spine: pollinate
Two modes. **Capture** files a proven element into a hive; **pull** brings
hive pollen into the current work. Ask which the user wants if the
invocation doesn't say. Read `${CLAUDE_PLUGIN_ROOT}/pollen/README.md` for
the record schema before writing any record.
## Hive configuration (both modes, first)
Read the invoking repo's dialect note (`docs/tracking-dialect.md` or
equivalent) for a `pollinate:` section listing hive repos and each hive's
visibility. If absent, interview — never assume:
1. "Which repo is your hive (where pollen records live)?" Accept several;
record each as `owner/repo (public|private)`.
2. If the builder works across public and privatevia SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有