From opentasks
Use when the user mentions a repository, Aone app, local path, cloned repo, moved repo, deleted repo, repo membership, or asks where code lives in an OpenTasks workspace.
How this skill is triggered — by the user, by Claude, or both
Slash command
/opentasks:opentasks-repo-indexThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for local repository lookup and OpenTasks repo membership. `info-for-agent/repo-index.md` is the Markdown source of truth for local paths and the boundary for automatic OpenTasks enablement. Durable project/repo relationships belong to `opentasks-repo-map`.
Use this skill for local repository lookup and OpenTasks repo membership. info-for-agent/repo-index.md is the Markdown source of truth for local paths and the boundary for automatic OpenTasks enablement. Durable project/repo relationships belong to opentasks-repo-map.
Use this skill when the user:
For simple OpenTasks repo list/add/remove/update/validate requests, use the Atomic Path. Do not run opentasks context, do not read task or memory files, and do not inspect repo-map.md before the command. opentasks repo validate will check repo-map references when needed.
If the user is in the OpenTasks workspace and asks to read, inspect, modify, build, or summarize another local repository path that is not indexed yet, first add that repository with the Atomic Path and validate. Then use the resolved local path for the requested work.
Use this path only for direct repo membership commands.
opentasks workspace show or use the explicit --cwd.opentasks repo list|add|remove|update|validate --cwd "<workspace>".opentasks repo validate --cwd "<workspace>".Use this path when the user needs a local repo found, opened, inspected, cloned, moved, or removed as part of broader work.
info-for-agent/repo-index.md or run opentasks repo list.仓库简称远程仓库说明opentasks repo add.opentasks repo update.opentasks repo remove; this removes OpenTasks management only, not the local repository directory.Use this path only when the request spans project names, multiple repos, version relationships, dependency relationships, or "must check together" rules.
opentasks-repo-map.opentasks repo validate after repo-map edits.repo-map references unmanaged repo by adding the repo to repo-index.md or removing the stale repo-map reference.Add the current repo:
opentasks repo add .
Add a specific repo:
opentasks repo add "/path/to/repo" \
--name "<repo-name>" \
--description "<short description>"
List and validate:
opentasks repo list
opentasks repo validate
opentasks repo validate checks indexed paths/remotes and repo-map references. Every repo name used in repo-map.md must exist in repo-index.md.
Update moved repo path:
opentasks repo update "<repo-name>" --path "/new/path/to/repo"
Remove from OpenTasks management:
opentasks repo remove "<repo-name>"
opentasks repo remove also removes that repo from repo-map.md project rows, relationship rows, and cross-repo rules. The removed repo-index row and repo-map changes are stored together in trash, so opentasks trash restore --id <trash-id> restores both.
repo-index.md keeps paths:
Keep this format:
| 仓库简称 | 本地路径 | 远程仓库 | 说明 |
|---------|---------|---------|------|
| opentasks | `/Users/example/Desktop/opentasks` | `owner/opentasks` (github) | OpenTasks 插件 |
repo-map.md keeps relationships:
## Projects
| 项目 | 相关 repos | 说明 |
|------|------------|------|
## Relationships
| From | Relation | To | 说明 |
|------|----------|----|------|
## Cross-Repo Rules
| 如果修改 | 必须检查 | 原因 |
|----------|----------|------|
repo-index.md should not be auto-managed by OpenTasks hooks.repo-map.md; put it in tasks/{slug}/brief.md.repo-map.md only for durable cross-repo structure: projects, dependencies, version relationships, and check rules.\|.npx claudepluginhub zichaojin/opentasks --plugin opentasksCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.