Add GitHub permalinks with fixed SHA/commit references to research documentation containing code snippets. Use when writing technical docs with code examples, creating investigation/research docs that reference source files, user asks to "add permalinks" or "add GitHub links", documenting code research findings with file:line references, or creating audit trails needing permanent code references. Triggers on "add github links", "add permalinks", "link to source", "make code references permanent".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Add permanent GitHub file URLs to research documentation so code references don't break when files change.
Scan the document for code references to determine which repositories are involved:
# Common patterns to detect:
repos/{repo}/path/to/file.rb:123 → submodule repo
app/models/user.rb:45 → current repo
commit abc123 in org/repo → external repo
# For submodule repos
cd repos/{repo} && git rev-parse HEAD
# For current repo
git rev-parse HEAD
# For historical commits - use the commit SHA directly
Transform code block comments from local paths to GitHub permalinks:
Before:
# app/models/user.rb:45-50
def example_method
# implementation
end
After:
# app/models/user.rb:45-50
# https://github.com/{org}/{repo}/blob/{SHA}/app/models/user.rb#L45-L50
def example_method
# implementation
end
Convert plain file paths to clickable markdown links:
Before:
| File | Line | Content |
|---|---|---|
app/models/user.rb | 45 | method definition |
After:
| File | Line | Content |
|---|---|---|
app/models/user.rb | 45 | method definition |
Add a reference section at the top of Technical Notes or similar sections:
> **Reference SHAs (Permalinks):**
> - **{repo}**: [`{short_sha}`](https://github.com/{org}/{repo}/tree/{SHA}) (YYYY-MM-DD)
https://github.com/{org}/{repo}/blob/{SHA}/{path}#L{start}-L{end}
| Component | Example | Notes |
|---|---|---|
| org | myorg | GitHub organization or username |
| repo | myrepo | Repository name |
| SHA | c617ebdcda... | Full or short (10+ chars) commit SHA |
| path | app/models/user.rb | File path from repo root |
| #L{n} | #L45 | Single line anchor |
| #L{n}-L{m} | #L45-L50 | Line range anchor |
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Fetch Airbnb income estimate (ADR, occupancy, monthly revenue) for any area using the official Airbnb GraphQL API — the same data the Airbnb host simulator shows. Input: station/area name. Output: per-night rate, avg nights, monthly estimate for entire_home and private_room.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
やりたいことを1行で言うと、B 型 loop engineering の 7 要素 (context / feedback / verification gate / termination / error handling / state / cost guard) を埋めた loop spec をコピペ可能な形で生成する。生成した spec は現行 Claude Code の実行プリミティブ (Workflow ツール / /loop skill / ralph-loop plugin / claude -p) に落とせる骨格になる (旧 `claude --goal` は廃止)。10 件 failure mode (F1-F10) の対策フックも自動挿入。Hybrid モード: 1 行入力 → デフォルト埋めで一発出力 → 「ここを調整したい」場所だけ短く聞き直す。Use when ユーザーが「loop を作りたい / loop-design / 自走ループ書いて / Workflow 用の spec 作って / 7 要素埋めて / verification gate ありで」と言ったとき、または `/loop-design` を実行したとき。Loop engineering の理論背景は Cards/loop-engineering-autonomous-agents、失敗モード対策は Cards/loop-failure-modes-mechanism-2026 を参照。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a project's GitHub Issues through Orca Workers from a coordinating session in the project's Hub folder. The Orchestrator reads Issues, claims one, dispatches an Orca Task into a fresh worktree of the target repo, supervises until worker_done, and writes the outcome back to the Issue — it never edits code itself. Use when the user says "take
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts. Use when the user asks to show / diagram / visualize / sketch / illustrate what is going on, asks "what does this look like", "how does this flow", "show me the structure", or in Japanese 図で見せて / 図解して / 図にして / 構造を見せて / フローを見せて / 全体像を見せて / どうつながってるか見せて. Also use it proactively when an explanation is running long and a call tree, file tree, component tree, diff, Mermaid diagram, or a small HTML artifact would land faster than prose.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Vendor (copy-import) a single external Claude Code skill into your own skills repo correctly — with license compliance and full provenance/attribution. Deterministic, idempotent primitive: given an upstream ref (owner/repo/path@sha or a GitHub URL) it fetches the skill, detects and gates on the license, copies the folder, injects a provenance frontmatter block (license + metadata: author/source/upstream_commit/vendored_at/provenance), ships the upstream LICENSE, adds a ## Credits section, and records a CREDITS.md ledger entry. Use when the user asks to "vendor a skill", "import a skill", "clone a skill", "borrow someone's skill", "add an external skill with attribution/credit", or スキルを取り込む / vendoring / 他人のスキルを自分のリポに取り込む. This is the import primitive that a skill-scout/curator orchestrator calls; it does NOT discover or evaluate — it correctly imports ONE skill you already chose.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate PPTX slide decks from a speech script or talking points — built for the 5-minute Monday morning speeches at Syla. Use when the user already has a script / 原稿 / メモ and asks to turn it into slides, a deck, or a presentation. Not for slides derived from a video — use youtube-slide-maker for that. Uses PptxGenJS directly (NOT html2pptx.js). Provides 4 slide template patterns, D3.js chart generation, and AI image integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.