Skip to content

Worktree feat+bitbucket azure platforms - #12

Merged
Dropelikeit merged 2 commits into
mainfrom
worktree-feat+bitbucket-azure-platforms
May 12, 2026
Merged

Worktree feat+bitbucket azure platforms#12
Dropelikeit merged 2 commits into
mainfrom
worktree-feat+bitbucket-azure-platforms

Conversation

@Dropelikeit

Copy link
Copy Markdown
Owner

No description provided.

  Extend the resolve-comments skill from GitHub + GitLab to four
  platforms with a user-selectable CLI or MCP authentication path per
  platform. Split the source into a thin orchestrator (core/kernel.md)
  plus per-platform modules (core/platforms/{github,gitlab,bitbucket,
  azure}.md). The build pipeline emits each platform module as a
  sibling file next to every agent's SKILL.md.

  New platforms
  - Bitbucket Cloud: CLI via `acli` or MCP via the official Atlassian
    Remote MCP server (`https://mcp.atlassian.com/v1/sse`, OAuth — no
    PAT required).
  - Azure DevOps: CLI via `az` plus the `azure-devops` extension, or
    MCP via `@azure-devops/mcp` with the PAT supplied through an env
    variable. The token value is never written to disk; the skill
    records only the env-variable name and a `${ENV_VAR}` reference
    in the MCP server config.

  Orchestrator and shared infra
  - New kernel Step 1.3 centralises the CLI-vs-MCP auth-method prompt
    for Bitbucket and Azure; GitHub and GitLab are unchanged (always
    CLI). Memory schema gains `Auth method`, `MCP server id`,
    `Token env var`, and `Org / Workspace` fields.
  - Reusable MCP Config Writer snippet: read → diff → AskUserQuestion
    (Overwrite / Keep existing / Abort) → write. Never silently mutates
    an existing `mcpServers.<id>` entry. Verifies the named env
    variable is set before writing.
  - Build (`scripts/build.sh`), validate (`scripts/validate.py`), and
    smoke test (`tests/build_test.sh`) extended to assert per-platform
    module presence, content markers, and a negative regex rejecting
    literal-looking PATs in the Azure module.

  Docs and release plumbing
  - README documents both CLI and MCP setup for the two new platforms
    in the existing GH/GL style (prerequisites tables, MCP config
    examples, env-var setup).
  - CHANGELOG entry for 1.0.0.
  - All six adapter manifest version fields bumped to 1.0.0;
    Augment and Codex manifest descriptions and keyword/tag arrays
    updated to mention all four platforms.
  - Adapter frontmatter and prelude opening lines updated across all
    five agents (claude, codex, augment, junie, roo).

  Compatibility
  - Existing GitHub and GitLab project memories without `Auth method`
    continue to work — they are read as `cli`. No migration required.
  - Codex adapter intentionally retains no persistence layer; its MCP
    Config Writer snippet is a stub directing users to configure their
    host manually.

  BREAKING CHANGE: The source layout splits core/kernel.md into a thin
  orchestrator plus per-platform modules under core/platforms/. The
  platform memory schema gains required fields (Auth method, MCP server
  id, Token env var, Org / Workspace) for the new platforms. The build
  pipeline now emits a platforms/<name>.md sibling for every SKILL.md
  per agent. Anyone consuming core/ or the generated layout
  programmatically should re-test against the new tree.
@Dropelikeit Dropelikeit self-assigned this May 12, 2026
@github-actions github-actions Bot added documentation Improvements or additions to documentation skill:resolve-comments plugin:config labels May 12, 2026
@Dropelikeit
Dropelikeit merged commit b2d3172 into main May 12, 2026
3 checks passed
@Dropelikeit
Dropelikeit deleted the worktree-feat+bitbucket-azure-platforms branch May 12, 2026 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation plugin:config skill:resolve-comments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant