opentasks-repo-map

OpenTasks Repo Map

Use this skill after using-opentasks routes durable project/repo relationship work here. info-for-agent/repo-map.md records long-lived structure. It is not a task log.

When To Use

Use this skill when the user says:

• several repositories belong to one project
• one repository installs, depends on, adapts to, or versions with another repository
• changes in one repository require checking another repository
• they want to update the repo map, repo wiki, project map, or cross-repo rules

Commands

Add or update a project row:

opentasks repo-map project add \
  --project "<project-name>" \
  --repo "<repo-name>" \
  --repo "<repo-name>" \
  --description "<short durable description>"

Add a relationship row:

opentasks repo-map relation add \
  --from "<repo-name>" \
  --relation "<relation-name>" \
  --to "<repo-name>" \
  --description "<short durable description>"

Add a cross-repo check rule:

opentasks repo-map rule add \
  --if-modify "<repo-name>" \
  --must-check "<repo-name>" \
  --reason "<why this needs checking>"

Validate:

opentasks repo-map validate

Rules

• Every repo referenced in repo-map must already exist in info-for-agent/repo-index.md.
• If a repo is missing, route to opentasks-repo-index first and add it with opentasks repo add.
• Put task-specific requirements in tasks/{slug}/brief.md, not repo-map.
• Put task-local repo/project links in the task brief ## 关联 table.
• Keep repo-map rows stable, concise, and human-readable.
• When the user gives explicit project/repo/relationship values, run the CLI directly and validate; do not load full task or memory context just to update repo-map.
• Run opentasks repo-map validate after edits.