worktree-init-script
**UNIVERSAL TRIGGER**: Use when creating git worktrees in projects with init.sh - extends using-git-worktrees to run project-specific initialization script after worktree setup. **Activation**: Automatic when `using-git-worktrees` is invoked and `init.sh` exists in project root. **Setup**: "run init.sh", "initialize worktree", "project setup script" **Create**: "create worktree", "set up workspace", "new worktree" **Check**: "check init.sh", "verify project setup" TRIGGERS: init.sh, worktree init, worktree setup, project setup script, run init, initialize worktree, worktree initialization, create worktree init, setup worktree project, инициализация worktree, запустить init.sh, скрипт инициализации, настройка worktree, создать worktree с init
Best use case
worktree-init-script is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
**UNIVERSAL TRIGGER**: Use when creating git worktrees in projects with init.sh - extends using-git-worktrees to run project-specific initialization script after worktree setup. **Activation**: Automatic when `using-git-worktrees` is invoked and `init.sh` exists in project root. **Setup**: "run init.sh", "initialize worktree", "project setup script" **Create**: "create worktree", "set up workspace", "new worktree" **Check**: "check init.sh", "verify project setup" TRIGGERS: init.sh, worktree init, worktree setup, project setup script, run init, initialize worktree, worktree initialization, create worktree init, setup worktree project, инициализация worktree, запустить init.sh, скрипт инициализации, настройка worktree, создать worktree с init
Teams using worktree-init-script should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/worktree-init-script/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How worktree-init-script Compares
| Feature / Agent | worktree-init-script | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
**UNIVERSAL TRIGGER**: Use when creating git worktrees in projects with init.sh - extends using-git-worktrees to run project-specific initialization script after worktree setup. **Activation**: Automatic when `using-git-worktrees` is invoked and `init.sh` exists in project root. **Setup**: "run init.sh", "initialize worktree", "project setup script" **Create**: "create worktree", "set up workspace", "new worktree" **Check**: "check init.sh", "verify project setup" TRIGGERS: init.sh, worktree init, worktree setup, project setup script, run init, initialize worktree, worktree initialization, create worktree init, setup worktree project, инициализация worktree, запустить init.sh, скрипт инициализации, настройка worktree, создать worktree с init
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Worktree Init Script Extends `superpowers:using-git-worktrees` -- after creating a worktree, runs `./init.sh` if the script exists in the project root. **Core principle:** Project-specific initialization via a single script replaces auto-detect heuristics. ## When to Use **Automatically activates** when: - `using-git-worktrees` is invoked - Project root contains executable `init.sh` ## Integration with using-git-worktrees **Modifies step "Run Project Setup":** Instead of auto-detecting by package.json/Cargo.toml: 1. Check for `init.sh`: ```bash [ -x ./init.sh ] && echo "init.sh found" ``` 2. If `init.sh` exists and is executable -- run it: ```bash ./init.sh ``` 3. If `init.sh` does not exist -- fall back to standard `using-git-worktrees` logic ## Quick Reference | Situation | Action | |-----------|--------| | `init.sh` exists and executable | Run `./init.sh` | | `init.sh` does not exist | Standard setup (npm/cargo/etc) | | `init.sh` fails | Report error, ask whether to continue | ## Template A ready-made template is available at `templates/init.sh` in this plugin (mise, submodules, envrc, direnv).
Related Skills
zellij-tab-pane
**UNIVERSAL TRIGGER**: OPEN/CREATE/RUN tab or pane IN zellij. Modes: empty tab/pane, shell command in tab/pane, Claude session in tab/pane, GitHub issue in tab/pane. Examples: "open new tab", "run npm test in pane", "execute plan in tab", "start issue #123 in pane", "открой вкладку", "запусти тесты в панели", "делегируй в вкладку", "стартани issue в панели"
task-routing
**UNIVERSAL TRIGGER**: ROUTE/TAKE/IMPLEMENT any task FROM a URL or issue reference **URLs & References**: - "get task from github.com/.../issues/N", "fetch spec from docs.google.com/..." - "retrieve task from https://..." **Local File Paths**: - "реализуй /path/to/plan.md", "выполни ./docs/plans/fix.md" - "take /home/user/plan.md", "implement /abs/path/to/plan.md" **Action Triggers (EN)**: - "take this task", "implement this spec", "do issue #NNN" - "route task", "route this", "start issue #NNN" - "check this task", "analyze task" **Triggers (RU)**: - "возьми задачу", "сделай задачу", "реализуй по спеке" - "сделай issue #NNN", "возьми issue #NNN" **#NNN**: action-слово + "issue"/"задачу" обязательны. Голый #NNN -- НЕ триггер. **Should NOT activate** (handled by other skills): - "show/read/view issue #N" (github-issues) - "what does issue #N say" (github-issues) - "edit/close/mark done issue" (github-issues) - "review spec", "check spec", "analyze requirements" (spec-review) - bare GitHub issue URL without action verb (github-issues) TRIGGERS: route task, route this, возьми задачу, сделай задачу, take this task, implement this spec, implement this issue, get task from, check this task, analyze task, retrieve spec, fetch task, реализуй по спеке, сделай issue, do issue, start issue, github.com/issues, docs.google.com/document, /docs/plans, ./docs/plans, /tmp/plan, local file, локальный файл
spec-review
**UNIVERSAL TRIGGER**: Ревью спецификаций и ТЗ на гапы, нестыковки и противоречия. Используй когда: - "get/show/list/display spec issues", "retrieve spec analysis" - "check/analyze/fetch spec review", "review spec" - "проверь спецификацию/ТЗ", "ревью спеки", "проанализируй ТЗ" - "найди гапы в требованиях", "найди нестыковки/противоречия" - пользователь дал ссылку на Google Doc, GitHub issue или Docmost-документ со спецификацией - пользователь вставил текст спецификации и просит проверить **Уровни глубины**: - `--quick` / `-q` — только критические блокеры (быстро) - `--standard` / `-s` — критические + высокие (по умолчанию) - `--deep` / `-d` — все проблемы включая средние - `--exhaustive` / `-e` — полный аудит с рекомендациями - `--no-ask` — использовать standard без вопроса (для CI/CD) **Ключевые слова для уровней**: - "быстро проверь", "только блокеры" -> quick - "тщательно", "подробно", "глубоко" -> deep - "полный аудит", "исчерпывающий" -> exhaustive **Google Doc**: - "проверь спеку docs.google.com/document/d/XXX" - "ревью этого ТЗ [ссылка на Google Doc]" **Docmost**: - "проверь спеку https://docs.company.com/p/XXXXXXXX" - "ревью этого ТЗ в Docmost [ссылка]" **GitHub Issue** (ТОЛЬКО с ревью-контекстом!): - "проанализируй issue #123" (ревью-слово: "проанализируй") - "проверь спецификацию github.com/.../issues/456" (ревью-слово: "проверь") - голый "issue #123" без ревью-контекста -- НЕ триггер (github-issues или task-routing) **Текст в сообщении**: - "проверь это ТЗ: [текст спецификации]" - пользователь вставил большой текст и просит ревью **Локальный файл**: - "проверь спеку в docs/spec.md" - "сделай ревью файла requirements.txt" TRIGGERS: спецификация, ТЗ, spec, specification, requirements, проверь спеку, ревью спеки, review spec, analyze spec, найди гапы, найди противоречия, найди нестыковки, docs.google.com/document, github.com/issues, docmost, /p/, техническое задание, требования, acceptance criteria, проанализируй требования, check requirements, --quick, -q, --deep, -d, --exhaustive, -e, --no-ask, быстро проверь, тщательно проанализируй, полный аудит, только блокеры, глубокий анализ, исчерпывающий
pr-review-fix-loop
**UNIVERSAL TRIGGER**: Iterative PR review + autofix loop. Use when user wants to review, check, or fix PR changes automatically. Common patterns: - "review my PR", "check my PR", "review changes" - "fix review comments", "address review findings" - "run review loop", "autofix PR issues" - "проверь мой PR", "ревью PR", "проверь изменения" - "исправь замечания ревью", "пофикси замечания" - "запусти ревью", "автоисправление PR" **PR Review** (iterative review + fix cycle): - "review and fix my PR", "check PR and fix issues" - "iterate on PR review", "review loop" - "проверь и исправь PR", "итеративное ревью" **Code Review Fix** (address existing review comments): - "fix review comments", "address PR feedback" - "fix code review issues", "resolve review findings" - "исправь замечания", "пофикси комментарии ревью" **Codex Review** (standalone Codex CLI review): - "codex review", "run codex on my changes" - "codex ревью", "запусти codex" TRIGGERS: review PR, check PR, fix PR, review changes, review loop, autofix, pr review, code review fix, address review, fix comments, review findings, iterate review, codex review, run codex, проверь PR, ревью PR, исправь замечания, пофикси PR, проверь изменения, запусти ревью, автоисправление, codex ревью, замечания ревью, фикс PR
media-upload
**UNIVERSAL TRIGGER**: Use when user wants to UPLOAD/SAVE/ATTACH/SHARE images or media files to S3. **AUTO-TRIGGER**: Activate AUTOMATICALLY after taking screenshots with Playwright MCP. Common patterns: - "upload/save/attach/share [file] to s3" - "get/fetch public link for [image]" - "show/list/display recent uploads" - "сделай скриншот и сохрани" (screenshot + upload) - "открой сайт и сделай скриншот" (implies upload) **Screenshots** (AUTO-ACTIVATE after Playwright screenshot): - After `browser_take_screenshot` → automatically offer to upload - "upload screenshot", "save screenshot", "attach screenshot" - "загрузи скриншот", "приложи скриншот", "сохрани скриншот" - "сделай скриншот [сайта]" → take screenshot + upload to S3 ️ **Images**: - "upload/save/attach image/picture/photo" - "share png/jpg/gif", "get link for image" **Batch**: - "upload all png from ./folder/" - "загрузи все картинки" **History**: - "show/list recent uploads" - "покажи загрузки" TRIGGERS: upload, save, attach, share, get link, show uploads, list uploads, screenshot, image, picture, photo, png, jpg, gif, webp, svg, pdf, s3, bucket, cdn, minio, public link, скриншот, картинка, загрузи, сохрани, сделай скриншот, take screenshot, browser_take_screenshot, playwright screenshot
long-running-harness
**UNIVERSAL TRIGGER**: Use when user wants to START/CONTINUE/MANAGE a long-running development project across multiple sessions. Common patterns: - "start/init/begin new project [description]" - "continue/resume working on [project]" - "начать/инициализировать проект", "продолжить работу над проектом" - "set up harness for [project]", "create project scaffolding" Session types supported: **Initialize (first run)**: - "init long-running project", "start new multi-session project" - "set up project harness", "create progress tracking" - "initialize [web-app/api/cli] project", "начать долгий проект" **Continue (subsequent sessions)**: - "continue project", "resume work", "продолжить работу" - "pick up where I left off", "what's next", "следующая фича" - "next feature", "continue implementation" **Status & Progress**: - "show project progress", "what features are done" - "project status", "статус проекта", "что сделано" - "remaining features", "what's left to do" **Management**: - "mark feature as done", "update progress" - "add new feature to list", "reprioritize features" Context patterns: - "get/show/list project progress" - "check project status" - "what features in project" - "display remaining features" - "fetch session history" - "retrieve progress log" TRIGGERS: long-running, multi-session, project harness, initialize project, continue project, resume work, progress tracking, feature list, session handoff, incremental development, cross-session, долгий проект, продолжить работу, прогресс проекта, следующая сессия, инициализация проекта, get project status, show features, list remaining, check progress, display status, fetch history, retrieve log, what features done, start harness, begin project, resume session, next feature, pick up work, update progress, mark done, end session Based on Anthropic's research on effective harnesses for long-running agents. Source: https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents
himalaya
**UNIVERSAL TRIGGER**: Use when user wants to READ/SEND email. Common patterns: - "check my email/inbox", "show unread" - "send email to [recipient]" - "проверить почту", "отправить письмо" **Reading**: - "check inbox", "show unread emails", "what's in my mail" - "read email from [sender]", "find emails about [topic]" - "show email folders", "list mail folders" - "проверить входящие", "непрочитанные", "что в почте", "покажи папки" **Sending**: - "send email to [address]", "compose email" - "reply to email", "forward email" - "отправить письмо", "ответить на письмо", "написать письмо" **Accounts**: - "list email accounts", "switch to work email" - "список почтовых аккаунтов", "использовать рабочую почту" ❌ **Should NOT activate**: - "what is SMTP protocol" (general question) - "email regex validation" (programming) - "install himalaya" (setup) TRIGGERS: email, mail, inbox, send, check, read, show, list, get, compose, reply, forward, unread, fetch, view, display, folder, folders, отправить, проверить, прочитать, показать, получить, письмо, почта, папка, папки
plan-to-issue
**UNIVERSAL TRIGGER**: SAVE/PUBLISH/EXPORT implementation plan TO GitHub issue for separate session execution. Common patterns: - "save/publish/export plan to issue" - "create issue from plan", "plan to github" - "сохрани план в issue", "создай issue из плана" **Save Plan**: - "save plan to issue", "publish plan to github" - "сохрани план в issue", "экспортируй план" **Create Issue from Plan**: - "create issue from plan", "plan as issue" - "создай issue из плана", "план в задачу" **Execute Later**: - "save for separate session", "execute plan later" - "сохрани для отдельной сессии", "выполнить потом" **Should NOT activate**: - General "create issue" without plan context - Reading existing issues - Working with issue checkboxes TRIGGERS: plan to issue, save plan, export plan, publish plan, plan as issue, issue from plan, plan to github, сохрани план, план в issue, экспорт плана, план в задачу, save for later, execute later, separate session, сохрани для сессии, выполнить потом, план в github
github-issues
**UNIVERSAL TRIGGER**: Use when user mentions GitHub issue URL or asks to read/work with GitHub issues. **Default handler**: Bare GitHub issue URL without action verb -> github-issues (read mode). If user sends just a URL like "https://github.com/org/repo/issues/42" with no action word, this skill handles it. **CRITICAL RULE**: ALWAYS use `gh` CLI for GitHub issues, NEVER use WebFetch! **Reading**: "read issue #N", "show issue", "прочитай задачу" ✅ **Checkboxes**: "mark done", "complete step", "отметь пункт" **Sub-issues**: "create sub-issue", "link as child", "подзадача" **Management**: "edit issue", "close issue", "add label" ️ **Images**: "download images from issue", "скачать картинки" TRIGGERS: github.com/issues, issue #, read issue, show issue, view issue, прочитай issue, покажи issue, задача ✅ checkbox, mark done, complete step, check off, отметь пункт, закрой этап sub-issue, subtask, child issue, parent issue, подзадача, создай подзадачу edit issue, close issue, reopen issue, issue labels, create issue, update task ️ download images, issue attachments, скачать картинки
doc-validate
**UNIVERSAL TRIGGER**: Validate/check/lint documentation quality. **Formatting**: "validate docs", "doc lint", "проверь документацию" **Links**: "broken links", "orphan docs", "битые ссылки" **Terms**: "check glossary", "терминология", "synonyms" **Viewpoints**: "check artifacts", "state diagrams", "threat model" ⚡ **Contradictions**: "find conflicts", "противоречия" ️ **Gaps**: "missing coverage", "пробелы", "completeness" **Review**: "full audit", "полный аудит", "/doc:review" TRIGGERS: doc lint, validate docs, проверь документацию, broken links, orphan, glossary, viewpoints, contradictions, gaps, coverage, /doc:lint, /doc:links, /doc:terms, /doc:viewpoints, /doc:contradictions, /doc:gaps, /doc:review
bugsnag
**UNIVERSAL TRIGGER**: Use when user wants to GET/FETCH/RETRIEVE any data FROM Bugsnag. Common patterns: - "get/show/list/display [something] from bugsnag" - "получить/показать/вывести [что-то] из bugsnag" - "bugsnag [organizations/projects/errors/details/events/comments/stats]" - "what [data] in bugsnag", "check bugsnag [resource]" Specific data types supported: **Organizations & Projects**: - "list bugsnag organizations/orgs", "show organizations" - "list bugsnag projects", "available projects", "проекты bugsnag" **Errors (viewing)**: - "show/list bugsnag errors", "что в bugsnag", "check bugsnag" - "open errors", "error list", "ошибки bugsnag", "открытые ошибки" - "errors with severity error/warning", "filter bugsnag errors" **Error Details**: - "bugsnag details for <id>", "error details", "детали ошибки" - "show stack trace", "error context", "what happened in error" - "events for error", "error timeline", "события ошибки" **Comments**: - "show comments for error", "error comments", "комментарии ошибки" - "bugsnag discussion", "what comments on error" **Analysis**: - "analyze bugsnag errors", "error patterns", "анализ ошибок" - "bugsnag statistics", "error trends", "что происходит в bugsnag" ✅ **Management** (write operations): - "mark as fixed/resolved", "fix error", "resolve error", "close error" - "закрыть ошибку", "отметить как решенную", "исправить ошибку" - "add comment to error", "comment on bugsnag error" - NOTE: Fix/Resolve/Close are synonyms - all mark error as resolved in Bugsnag TRIGGERS: bugsnag, получить из bugsnag, показать bugsnag, список bugsnag, bugsnag data, bugsnag info, check bugsnag, what in bugsnag, bugsnag status, error tracking, error monitoring, production errors, stack trace, bugsnag organizations, bugsnag projects, bugsnag errors, bugsnag details, bugsnag events, bugsnag comments, bugsnag analysis, ошибки в bugsnag, что в bugsnag, проверить bugsnag, данные bugsnag, fix error, resolve error, close error, закрыть ошибку, исправить ошибку, отметить как решенную This skill provides complete Bugsnag API integration for viewing and managing error tracking data via Ruby helper scripts.
transcript-search
Intelligent semantic search over voice memo and video transcript DuckDB databases. Use when searching transcripts for topics, colors, tabs, concepts, or any content. NEVER dump full transcript text — use sentence-level extraction with context windows.