跳到主内容
智客 ZICQ

技能库 智客分类:运维与云 project-references

Project References

查看您自己的 GitHub 保存库中的公约、模式和具体执行情况, 每当在你的代码库家族中发生某些事情的不确定性时使用这种技能——例如. Helm图结构,Kubernetes的表单,框架配置模式,Docker编译常规,CI/CD管道设置,或任何其他反复出现的建筑决定. 在猜出公约之前主动提出;在采用模式时,总是引用来源项目和路径。 当用户要求查看、更新或搜索参考寄存器,或生成GitHub动作触发器的概览/报告(推出、拉出、请求、时间表/加长)时,也可以使用.

6518 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

查看您自己的 GitHub 保存库中的公约、模式和具体执行情况, 每当在你的代码库家族中发生某些事情的不确定性时使用这种技能——例如. Helm图结构,Kubernetes的表单,框架配置模式,Docker编译常规,CI/CD管道设置,或任何其他反复出现的建筑决定. 在猜出公约之前主动提出;在采用模式时,总是引用来源项目和路径。 当用户要求查看、更新或搜索参考寄存器,或生成GitHub动作触发器的概览/报告(推出、拉出、请求、时间表/加长)时,也可以使用.

何时用

用户要求检查、更新或搜索参考寄存器,或生成跨寄存器的 GitHub 动作触发器(推出、拉出_请求、调度/加长)的概览/报告

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Project References、Instructions、Step 1: Check whether the relevant repo is already cloned、Step 2: Ask the user which reference project is most relevant、Step 3: Search targeted — file first, then grep、Step 4: Cite the source when adopting a pattern。 其中含规范建议的小节:分步指令、输入输出示例。

文件分析

文件分析:除 SKILL.md 外,正文引用了 scripts/clone-or-update.sh、references/search-patterns.md、scripts/sync-all.sh、scripts/list-workflow-triggers.sh,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Look up conventions, patterns, and concrete implementations from your own GitHub repositories checked out locally under ~/projects/referenzen/. Use this skill whenever there is uncertainty about how something is done in your codebase family — e.g. Helm chart structure, Kubernetes manifests, framework configuration patterns, Docker Compose conventions, CI/CD pipeline setup, or any other recurring architectural decision. Invoke it proactively before guessing at a convention; always cite the source project and path when a pattern is adopted. Also use when the user asks to check out, update, or search reference repositories, or to generate an overview/report of GitHub Actions triggers (push, pull_request, schedule/cron) across repositories.

Project ReferencesInstructionsStep 1: Check whether the relevant repo is already clonedStep 2: Ask the user which reference project is most relevantStep 3: Search targeted — file first, then grepStep 4: Cite the source when adopting a patternStep 5: Sync only when explicitly requestedExamplesExample 1: Looking up a Helm chart conventionExample 2: Checking out a new reference repoExample 3: Finding a configuration patternExample 4: Overview of GitHub Actions triggers

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
project-references
description
Look up conventions, patterns, and concrete implementations from your own GitHub repositories checked out locally under ~/projects/referenzen/. Use this skill whenever there is uncertainty about how something is done in your codebase family — e.g. Helm chart structure, Kubernetes manifests, framework configuration patterns, Docker Compose conventions, CI/CD pipeline setup, or any other recurring architectural decision. Invoke it proactively before guessing at a convention; always cite the source project and path when a pattern is adopted. Also use when the user asks to check out, update, or search reference repositories, or to generate an overview/report of GitHub Actions triggers (push, pull_request, schedule/cron) across repositories.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 4
  • scripts/clone-or-update.sh
  • references/search-patterns.md
  • scripts/sync-all.sh
  • scripts/list-workflow-triggers.sh

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「project-references」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-99b1bb5aed171317-%E9%A1%B9%E7%9B%AE%E5%8F%82%E8%80%83%E6%96%87%E7%8C%AE.html
请存为 .cursor/skills/project-references/SKILL.md 或 .claude/skills/project-references/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/dboeckli/ai-agent-skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/dboeckli/ai-agent-skills' --list

npx skills add 'https://github.com/dboeckli/ai-agent-skills' --skill 'project-references'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: project-references description: "Look up conventions, patterns, and concrete implementations from your own GitHub repositories checked out locally under ~/projects/referenzen/. Use this skill whenever there is uncertainty about how something is done in your codebase family — e.g. Helm chart structure, Kubernetes manifests, framework configuration patterns, Docker Compose conventions, CI/CD pipeline setup, or any other recurring architectural decision. Invoke it proactively before guessing at a convention; always cite the source project and path when a pattern is adopted. Also use when the user asks to check out, update, or search reference repositories, or to generate an overview/report of GitHub Actions triggers (push, pull_request, schedule/cron) across repositories." --- --- # Project References This skill manages a local mirror of your own GitHub repositories under `~/projects/referenzen/` and lets you look up conventions and implementation patterns without guessing or reading all repos blindly. All operations are **read-only** on the reference projects themselves. Only `git clone` and `git pull` write into that directory — never edits. --- ## Instructions ### Step 1: Check whether the relevant repo is already cloned ```bash ls ~/projects/referenzen/ ``` If the needed repo is missing, run `scripts/clone-or-update.sh owner/repo` to clone it first. ### Step 2: Ask the user which reference project is most relevant Do not scan all repos blindly — that fills context. Ask: "Which of your sibling projects uses this pattern?" or list the available repos and let the user pick. ### Step 3: Search targeted — file first, then grep Use `find` to locate a file by name, then `cat` or `grep` to read only the relevant section. For search commands and patterns, consult `references/search-patterns.md`. ### Step 4: Cite the source when adopting a pattern Always state which project and file path a pattern came from before applying it: > Pattern adopted from `your-service` → `helm-charts/Chart.yaml` line 4 ### Step 5: Sync only when explicitly requested Run `scripts/sync-all.sh` only when the user says "sync all" or "update all references". For a single repo, prefer `scripts/clone-or-update.sh`. --- ## Examples ### Example 1: Looking up a Helm chart convention User says: "How should I structure the Helm chart for this project?" Actions: 1. Run `ls ~/projects/referenzen/` to see available repos 2. Ask: "Which sibling project should I use as reference?" — user says `your-service` 3. Run `find ~/projects/referenzen/your-service -name "Chart.yaml"` to locate it 4. Read the file, note the structure (apiVersion, dependencies, version pattern) 5. Apply the same structure; cite: "adopted from `your-service/helm-charts/Chart.yaml`" Result: Helm chart consistent with sibling projects, traceable source cited. ### Example 2: Checking out a new reference repo User says: "Clone my other-service project as a reference" Actions: 1. Run `bash scripts/clone-or-update.sh owner/other-service` 2. Stream output so user sees CLONE/PULL/SKIP progress 3. Confirm with `ls ~/projects/referenzen/other-service/` Result: Repo available locally for pattern lookups; no edits made. ### Example 3: Finding a configuration pattern User says: "How do I configure the database pool like in the other projects?" Actions: 1. `ls ~/projects/referenzen/` — pick a relevant sibling project 2. `grep -rn "database.pool" ~/projects/referenzen/your-service/src/main/resources/` 3. Read the relevant config section 4. Cite: "pattern from `your-service/src/main/resources/application.yaml` line 42" Result: Exact config from a proven sibling project, not guessed. ### Example 4: Overview of GitHub Actions triggers User says: "When do my projects run their GitHub Actions — push, PR, or schedule?" Actions: 1. Run `bash scripts/list-workflow-triggers.sh` (add `--glob` to narrow to one pipeline, `--root` for a different checkout directory) 2. Present the sorted overview (weekday/time, human-readable plus original cron) and the event-only workflows 3. Point the user to the generated report at `target/workflow-triggers.md` Result: Consolidated, time-sorted trigger overview across all reference repos plus a Markdown report, without opening each workflow file. --- ## Repository source Two sources are supported — prefer the manual list when it exists: 1. **Manual list** (`~/claude-shared/projekte.txt`): one GitHub repo URL or `owner/name` slug per line, blank lines and `#` comments ignored. 2. **Automatic discovery**: `gh repo list --limit 200 --json nameWithOwner` when the file is absent or the user explicitly asks for a full sync. --- ## Scripts Two ready-made scripts live in `scripts/` — use them instead of writing inline Bash. Both accept `REFERENZEN_DIR` as an env override (default: `~/projects/referenzen`). ### `scripts/clone-or-update.sh ` Clones a single repository or pulls if it already exists locally. Refuses to pull when local changes are present (exit code 2) — never stashes or resets. ```bash bash scripts/clone-or-update.sh owner/your-repo ``` Exit codes: `0` = ok, `2` = skipped (local changes), `3` = clone/pull failed. ### `scripts/sync-all.sh [--list ] [--limit ]` Iterates over all repositories and calls the clone-or-update logic for each. Prefers `~/claude-shared/projekte.txt` as source; falls back to `gh repo list` when the file is absent. Prints a summary line at the end. ```bash # Sync everything (auto-detect source) bash scripts/sync-all.sh # Use a specific list file bash scripts/sync-all.sh --list ~/claude-shared/projekte.txt # Limit gh repo list to 50 repos bash scripts/sync-all.sh --limit 50 ``` **Do not** run sync-all blindly — use it only when the user explicitly says "sync all" or "update all references". For a single repo prefer `clone-or-update.sh`. ### `scripts/list-workflow-triggers.sh [--root ] [--glob ] [--out ] [--no-report]` Scans every repo checkout for `.github/workflows/*.yml` and `*.yaml`, extracts the triggers from the `on:` block (`push`, `pull_request`, `schedule`, `workflow_dispatch`, `release`, …) plus any `cron:` expressions, prints the overview and writes a Markdown report. Scheduled workflows are **sorted by weekday/time** and shown with a **human-readable run time** (e.g. `Monday 02:05`) next to the **original cron expression**; workflows without a schedule are listed in a separate event-only section. Read-only, no network access. - `--root ` — directory containing repo checkouts. Default: `$REFERENZEN_DIR` or `~/projects/referenzen`. - `--glob ` — optional filename filter, e.g. `maven-build.yml`. Default: all workflows. - `--out ` — Markdown report path. Default: `target/workflow-triggers.md` (relative to the current project directory, created if missing). - `--no-report` — print to stdout only, skip the report file. ```bash # Overview + report for all reference repos bash scripts/list-workflow-triggers.sh # Only maven-build.yml, custom report location bash scripts/list-workflow-triggers.sh --glob 'maven-build.yml' --out target/maven-triggers.md # A different checkout root (e.g. Windows mount) bash scripts/list-workflow-triggers.sh --root /mnt/c/Development/projects/all-git-repos ``` --- ## Workflows ### 1. Check out or update repositories Run the appropriate script and stream output so the user sees every CLONE / PULL / SKIP action as it happens. ### 2. Search within reference projects Scope the search to what the user actually needs. Prefer targeted lookups over broad recursive greps. For ready-made search commands and citing patterns, consult `references/search-patterns.md`. ### 3. Discover available reference projects ```bash ls ~/projects/referenzen/ ``` If `~/claude-shared/projekte.txt` exists, show its contents alongside to explain which repos are tracked vs. which are locally present. ### 4. Overview of GitHub Actions triggers Run `scripts/list-workflow-triggers.sh` to get a cross-repo overview of every workflow's `on:` triggers and `cron:` entries. It also writes the report to `target/workflow-triggers.md`. Use `--glob` to focus on a single pipeline (e.g. `maven-build.yml`) and `--root` for a different checkout directory. --- ## When to suggest this skill proactively Suggest looking up a reference project when: - The user asks how something is structured and the answer may vary by project convention (Helm chart layout, Flyway migration naming, Dockerfile patterns, Maven plugin ordering, etc.) - There is more than one reasonable approach and consistency with sibling projects matters - The user says "like the other projects" or "same as before" without specifying which project Ask the user which reference project is most relevant rather than scanning all of them — scanning is expensive in context. --- ## Safety rules - Never edit, stage, commit, or delete files inside `~/projects/referenzen/`. - If `git pull` would fail due to local changes, report the conflict clearly and stop — do not stash, reset, or force. - Do not expose repository contents that contain secrets (`.env`, credential files) in the response — read and cite structure only.

相关技能

运维与云

Docker Essentials

用于容器管理,图像操作,调试的基本道克命令和工作流程.

运维与云

Find Skills

从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…

运维与云

Microsoft Foundry

构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…

运维与云

Azure Deploy

执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…