Productivity

tomevault-io Bundle

コードの変更・コミット・PRを作成するときのGitワークフローガイドライン。変更の粒度、コミットメッセージの形式、PRの作成方法を定める。 Use when this capability is needed.

tomevault-io Bundle

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Use when this capability is needed.

tomevault-io Bundle

Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenSoul to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags. Use when this capability is needed.

tomevault-io Bundle

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Use when this capability is needed.

tomevault-io Bundle

Run pytest tests with automatic virtual environment activation. Use this skill whenever running tests, executing pytest, or when asked to "run tests", "test this", or any test execution task. Ensures venv is always activated before pytest runs. Use when this capability is needed.

tomevault-io Bundle

Meta-skill workflow orchestrator for bug investigation and resolution. Routes to debug, implement, test, and commit based on scope. Use when this capability is needed.

tomevault-io Bundle

Use when you have a spec or requirements for a multi-step task, before touching code

tomevault-io Bundle

Second calendar skill. Use when this capability is needed.

tomevault-io Bundle

Task-driven development workflow with TODO tracking. Use when user says "dev", "dev-workflow", or asks to work on tasks, develop features, or proceed with implementation. Use when this capability is needed.

tomevault-io Bundle

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs. Use when this capability is needed.

tomevault-io Bundle

Handles git operations including commit with locking and syncing with remote. Use for committing changes or syncing with origin.

tomevault-io Bundle

This skill should be used when the user asks to "create a commit", "generate commit message", "commit changes", "make a commit", mentions "conventional commits", or discusses commit message formatting. Provides guided workflow for creating properly formatted commit messages with line length validation and required trailers. Use when this capability is needed.

tomevault-io Bundle

How to approach work. Applies to all tasks including implementation, planning, investigation, design, review, and auditing. Use when this capability is needed.

tomevault-io Bundle

Auto-route a message to the best matching session based on repo name, task ID, or context. This skill is for the Manager session inside Workstation app. If you're in a standalone Claude Code session, suggest the user open the Workstation app and use this skill from the Manager terminal. Use when this capability is needed.

tomevault-io Bundle

Testing strategies and methodologies including TDD and E2E testing. Use when writing tests, implementing TDD workflow, or setting up E2E test infrastructure. Use when this capability is needed.

tomevault-io Bundle

Git workflow discipline — branch decisions before a task, an incremental local-commit rhythm (no immediate push), the six-section PR description, on-demand issue creation, and post-merge cleanup (local branch + remote ref + remote branch). Enforces no direct commits to main, isolated git worktrees (kept outside the repo, under ../ or ~/.worktree/), and pushing only after the whole feature is locally verified. TRIGGER when the user starts any non-main branch task (build a feature / fix a bug / open a branch), prepares to commit/push/open a PR, or cleans up after a merge. ｜ Git 开发流程纪律——覆盖"开始任务前的分支决策"、"阶段性本地 commit 节奏（不立即 push）"、"PR 描述六段式规范"、"按需建 issue 策略"、"合并后清理（本地分支 + 远程引用 + 远程分支）"。强制要求：禁止 main 直接提交、worktree 必须与 repo 隔离存放（置于 ../ 或 ~/.worktree/ 下）、整个功能本地验证后才推送。TRIGGER when：用户开始任何非 main 分支开发任务（"做个新功能"/"改 bug"/"开个分支"），或准备 commit/push/开 PR，或 PR 合并完成需要清理时。 Use when this capability is needed.

tomevault-io Bundle

Git best practices for version control and collaboration Use when this capability is needed.

tomevault-io Bundle

Manage TaskBridge development tasks using the structured todo workflow. Use when creating, listing, completing, or updating task files in todo_tasks/ directory. Use when this capability is needed.

tomevault-io Bundle

Release a new version of BranchBox. Use when the user says "release", "new version", "cut a release", "publish release", or "tag version". Handles version bumping, changelog updates, quality checks, and GitHub release workflow. Use when this capability is needed.

tomevault-io Bundle

Architectural design exploration for a feature. Takes a Basecamp todo URL or .md file, explores the codebase, and presents 2-3 competing approaches with tradeoffs. No code changes — exploration only. Use when user says "design this", "explore approaches", or invokes /design. Use when this capability is needed.

tomevault-io Bundle

Collaborative design and specification workflow for turning ideas into detailed, implementation-ready designs. Use for feasibility checks ("is X possible?", "can we do Y?"), design exploration, and full specification. Triggers on "let's build", "I want to add", "how should we", "is it possible", "what would it take", "design", "architect", "spec out", or any non-trivial feature request. Skip ONLY for trivial single-location changes (typo, rename, color change). Use when this capability is needed.

tomevault-io Bundle

Safe Git workflow - commit with conventional format and branch safety, create branches, reset with backup, and multi-repo status. Use when committing, creating branches, resetting, or checking git status in multi-repo workspaces. Use when this capability is needed.

tomevault-io Bundle

Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Clawdis to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags. Use when this capability is needed.

tomevault-io Bundle

Initialize a new feature workflow with git worktree. Use when the user wants to start a new feature, create an isolated development branch, says "init worktree", or needs to set up a feature branch for compounder workflow. Use when this capability is needed.

tomevault-io Bundle

Release workflow for a single Go repository following semantic versioning. Use when releasing a Go package, creating a new version tag, or preparing to publish a Go module. Use when this capability is needed.

tomevault-io Bundle

Google Workspace CLI (gogcli) for Gmail, Calendar, Drive, Tasks, Contacts, Classroom, Chat. Use when accessing Google services via command line, automating email/calendar operations, managing Google Drive files, or working with Google Tasks. Use when this capability is needed.

tomevault-io Bundle

Use jujutsu (jj) for all version control operations including commits, branches, merges, rebases, and repository management. Handles git workflow translation to jj equivalents. Use when this capability is needed.

tomevault-io Bundle

Create git commits with conventional commit messages. ALWAYS use this skill when committing code - whether user-requested or after completing a task. Triggers on "commit", "/commit", "make a commit", "git commit", "save changes", or any request to commit. Accepts optional context argument for commit message guidance. Use when this capability is needed.

tomevault-io Bundle

Use when executing Phase 3 of vrau workflow - implementing the approved plan

tomevault-io Bundle

Systematic bug fixing workflow with regression tests and PR creation. Use when the user asks to "fix a bug", "debug an issue", "resolve a problem", or provides error messages/failing tests to fix. Handles reproduction, root cause analysis, test creation, fix implementation, and PR submission. Use when this capability is needed.

tomevault-io Bundle

Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Razroom to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags. Use when this capability is needed.

tomevault-io Bundle

This skill should be used when the user asks to "make a release", "create a release", "cut a release", "release a new version", "publish a release", or mentions preparing for release. Provides comprehensive workflow for reviewing changes, updating changelog, determining semver bump, and publishing. Use when this capability is needed.

tomevault-io Bundle

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Use when this capability is needed.

tomevault-io Bundle

Persistent completion mode. Use when the user explicitly says `/ralph` or clearly wants you to keep iterating until the task is actually finished, repeating implement-verify-fix loops instead of stopping at partial progress. Use when this capability is needed.

tomevault-io Bundle

Git commits, pushes, and GitHub operations using tokenlean. Covers tl push (with multi-file safety guard), tl commit-prep, tl gh (bulk issue/PR/release operations). Use when committing, pushing, creating/closing/viewing issues, managing PRs, creating releases, or any git/GitHub workflow. Use when this capability is needed.

tomevault-io Bundle

Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.