Skip to content

feat(zed): skills, rules, mcp + git-transport root-path follow-ups - #1720

Merged
dyoshikawa merged 1 commit into
mainfrom
resolve-scraps
May 28, 2026
Merged

feat(zed): skills, rules, mcp + git-transport root-path follow-ups#1720
dyoshikawa merged 1 commit into
mainfrom
resolve-scraps

Conversation

@dyoshikawa

Copy link
Copy Markdown
Owner

Summary

This PR resolves three open maintainer-scrap issues together.

Zed: skills, rules, and MCP (#1705)

The zed target previously supported only ignore. This adds:

  • skillsZedSkill writing .agents/skills/<name>/SKILL.md (project) and ~/.agents/skills/ (global).
  • rulesZedRule writing the project .rules file (first in Zed's priority list) and the global ~/.config/zed/AGENTS.md. Root-only, since Zed reads exactly one rules file.
  • mcpZedMcp writing the context_servers key in .zed/settings.json (project) / ~/.config/zed/settings.json (global). Reads/writes merge into the existing JSON so the ignore feature's private_files (which shares the same file) is preserved. Env references pass through unchanged.

Registered all three in their processors, added gitignore entries, updated the README/docs support matrix, and added e2e happy-path cells (generate / import / global).

git-transport root-path follow-ups (#1718)

Follow-ups from the PR #1711 review:

  • Normalize skillsPath before the repo-root check so "./.", ".//", and Windows ".\\" also disable sparse-checkout instead of re-triggering the original bug.
  • Tighten the root-path regression test so it distinguishes fixed vs. unfixed behavior.
  • Add a wildcard (skills: ["*"]) × repo-root (path: ".") integration test in sources.test.ts.
  • Document that path: "" / "." / "./" fetches the whole repository root.

antigravity-cli subagents (#1706)

Verified via the official Antigravity docs (rendered with playwright-cli) that CLI subagents are defined/managed only at runtime — the interactive /agents panel and the invoke_subagent / define_subagent tools — or bundled inside plugins. There is no standalone, declarative per-agent file (analogous to geminicli's .gemini/agents/) that rulesync could generate, so subagents remain out of scope. Refined the migration guide to record this conclusion. No generator added.

Related issues

Test plan

  • pnpm cicheck (lint, types, format, 5799 unit/integration tests, content/spelling/secrets) — green
  • New unit tests: zed-skill.test.ts, zed-rule.test.ts, zed-mcp.test.ts
  • Updated git-client.test.ts and sources.test.ts
  • E2E: e2e-skills, e2e-rules, e2e-mcp pass with the new zed cells
  • pnpm dev gitignore produces no spurious diff

…llow-ups

Zed (#1705): add ZedSkill (.agents/skills/), ZedRule (root .rules + global ~/.config/zed/AGENTS.md), and ZedMcp (context_servers in .zed/settings.json, merged so the ignore feature's private_files survive). Register all three in their processors, add gitignore entries, update the README/docs support matrix, and add e2e cells. Previously the zed target only supported ignore.

git-transport (#1718): normalize skillsPath before the repo-root check so '\''./.'\'', '\''.//'\'' and Windows '\''.\\'\'' also disable sparse-checkout; tighten the root-path regression test to distinguish fixed vs unfixed; add a wildcard x repo-root integration test; and document that path '\''""'\''/'\''"."'\'' fetches the whole repository.

antigravity-cli subagents (#1706): confirmed via the official docs that CLI subagents are defined and managed only at runtime (the /agents panel and invoke_subagent/define_subagent tools) or bundled inside plugins, with no standalone declarative per-agent file rulesync could generate. Documented as out of scope in the migration guide.

Refs: #1705, #1718, #1706

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@dyoshikawa
dyoshikawa merged commit 19cbc97 into main May 28, 2026
11 of 15 checks passed
@dyoshikawa
dyoshikawa deleted the resolve-scraps branch May 28, 2026 22:48
@dyoshikawa

Copy link
Copy Markdown
Owner Author

@dyoshikawa Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant