opentasks-repo-index

OpenTasks Repo Index

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.

When To Use

Use this skill when the user:

• mentions a repository name, Aone app name, or local codebase
• asks you to find, open, inspect, clone, move, or delete a repository
• asks you to work across repositories
• clones a new repository during task work
• changes a repository path or removes a repository
• asks to add the current repo to OpenTasks
• asks which repos are managed by OpenTasks
• asks to validate whether indexed repo paths still exist

Atomic Repo Operations

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.

Atomic Path

Use this path only for direct repo membership commands.

1. Resolve the workspace with opentasks workspace show or use the explicit --cwd.
2. Resolve the repo path/name from the user's request.
3. Run opentasks repo list|add|remove|update|validate --cwd "<workspace>".
4. After add, remove, or update, run opentasks repo validate --cwd "<workspace>".
5. Report only the repo name/path and validation result.

Lookup Path

Use this path when the user needs a local repo found, opened, inspected, cloned, moved, or removed as part of broader work.

1. Read info-for-agent/repo-index.md or run opentasks repo list.
2. Match the user's repository, project, or Aone app name against:
   • 仓库简称
   • 远程仓库
   • 说明
   • local path basename
3. If a match exists, use the indexed local path directly.
4. If no match exists and the user wants this repo managed, add it with opentasks repo add.
5. If no match exists and the user provided a clone URL, clone it to the chosen local location, then add it.
6. If a repository path changes, update the existing row with opentasks repo update.
7. If a repository should stop being managed, use opentasks repo remove; this removes OpenTasks management only, not the local repository directory.

Cross-Repo Path

Use this path only when the request spans project names, multiple repos, version relationships, dependency relationships, or "must check together" rules.

1. Resolve local repo paths through the Lookup Path.
2. Route durable project/repo relationships and cross-repo rules to opentasks-repo-map.
3. Run opentasks repo validate after repo-map edits.
4. Fix repo-map references unmanaged repo by adding the repo to repo-index.md or removing the stale repo-map reference.

Commands

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.

Markdown Format

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

| 如果修改 | 必须检查 | 原因 |
|----------|----------|------|

Rules

• Do not introduce SQLite, JSON, YAML, or a separate repo-index lifecycle implementation for repo-index.
• Do not invent repository paths.
• Prefer existing indexed paths over asking the user.
• A repo not listed in repo-index.md should not be auto-managed by OpenTasks hooks.
• Do not record task-specific brief content in repo-map.md; put it in tasks/{slug}/brief.md.
• Use repo-map.md only for durable cross-repo structure: projects, dependencies, version relationships, and check rules.
• Keep rows concise and human-readable.
• Escape table pipes in cell values as \|.
• Preserve categories when adding rows; add a new category only when it improves scanning.