Portable context layer / ABVX tool

ID

Use this when the human and operator context must travel across repos and tools.

GitHub Docs SET integration

Role in stack Portable context

Best for

Operators, tool builders, and teams that need reusable human context instead of re-explaining the same workflow state in every repo or chat.

Where it fits

ID is the portable profile-and-hook layer. SET orchestrates repo workflows and hooks. agentsgen manages repo-scoped agent docs.

Current SET support

pre_task and weekly_review are orchestrated in CI-safe flows. Mutating hooks stay outside the default action path.

What it does

Defines portable human-AI context artifacts that can move across tools instead of staying trapped in one chat session.
Ships a lightweight CLI and repo-local integration hooks for practical execution paths.
Lets SET run explicit pre_task and weekly_review hooks in ID-compatible repositories.
Complements agentsgen by carrying person and workflow context across tools.

Portable artifacts

Human-first outcome: your operator context can move with the work instead of staying trapped in one tool session.

owner / target identity
repo-local hook configuration
portable execution context
lightweight integration metadata

Quickstart

Minimal SET-compatible example

- uses: markoblogo/SET@main
  with:
    workflow_preset: "repo-docs"
    repomap: "true"
    id_enabled: "true"
    id_owner_id: "markoblogo"
    id_target: "set"
    id_pre_task: "true"
    id_weekly_review: "true"
    path: "."

Current SET support is intentionally CI-safe: pre_task and weekly_review are orchestrated, while mutating hooks such as post_task stay outside the default Actions path.