Skip to content

daledesilva/obsidian_ink / .agents/skills/update-agent-tooling

update-agent-tooling

Verified

Sync Cursor, Devin, and Antigravity agent tooling from _reference_ide-setup into a target project.

FileKindSize
SKILL.mdskill md5.3 KB
---
name: update-agent-tooling
description: Sync Cursor, Devin, and Antigravity agent tooling from _reference_ide-setup into a target project.
---

# Update agent tooling from reference repo

Sync Cursor, Devin, and Antigravity agent tooling from `_reference_ide-setup` into a target project.

Any text after `/update-agent-tooling` is optional context, such as a target repo path, environment name, or specific tooling type to check.

## Scope

- Target the primary repository in the current workspace unless the user names another repo or path.
- Use `_reference_ide-setup` as the source of truth for reusable agent tooling.
- Pull in missing shared/common tooling from `shared/`.
- Detect this project type, then pull in missing relevant tooling from the matching environment folder, such as `android-native/`, `react-native/`, `web-react/`, `obsidian-plugin/`, or `unity-mixed-reality/`.
- Agent tooling includes Cursor commands, skills, rules; Devin skills/config; Antigravity skills, rules, and root `AGENTS.md`; scripts/templates they depend on, and docs that explain how to use them.
- Cursor tooling is copied to the target's `.cursor/`; Devin tooling is copied to the target's `.devin/`; Antigravity tooling is copied to the target's `.agents/` and root `AGENTS.md`.
- There is **no** shared ClickUp MCP JSON to copy. Point people at `shared/docs/cursor-mcp-clickup-cloud-agents.md` (and the root README ClickUp section) for the URL, global vs project vs Cloud Agents placement, **`~/.zshenv` `CLICKUP_API_TOKEN`** for REST reparenting, and **If nesting stops working**. Copy `shared/docs/cursor-mcp-clickup-cloud-agents.md` → target `docs/cursor-mcp-clickup-cloud-agents.md` and `shared/scripts/clickup-set-parent.sh` → target `scripts/clickup-set-parent.sh` when missing or when the reference copy is newer. Copy or merge environment `mcp.json` or `.devin/mcp_config.json` only when that environment still ships a project-bound server and it is missing from the target. Unity Editor control is the CLI (`unity pipeline install`, `unity skill install cursor --local`), not an MCP relay.
- Do not commit, push, or change branches unless the user explicitly asks.
- When the same path exists in reference and target, **newer overwrites older** — do not replace a newer target file with an older reference copy.

## Modification times

Before copying or overwriting any file that exists in both reference and target:

1. Compare last-modified timestamps on disk (`stat`, `ls -lt`, or equivalent — do not rely on git history alone).
2. **Missing in target** — copy from reference.
3. **Both exist, reference newer** — copy or merge reference content into target so recent reference edits replace stale target copies.
4. **Both exist, target newer** — skip overwrite; note in output that the project copy is ahead of reference.
5. **Timestamps within ~1 minute** — diff both versions and ask the user before overwriting.
6. Report which side was newer for each updated or skipped pair in the output.

## Steps

1. Resolve source and target:
   - Find `_reference_ide-setup` in the workspace or as a sibling repo.
   - Identify the target repo from the `/update-agent-tooling` context, or default to the primary repo in the workspace.
   - If either repo is ambiguous or missing, ask for clarification before editing.

2. Determine the environment:
   - Prefer an explicit environment named after the command.
   - Otherwise inspect project files, existing rules, README files, build files, and package metadata.
   - If the project type is still unclear, ask before copying environment-specific tooling.

3. Compare tooling:
   - **Cursor:** Check `shared/.cursor/commands/`, `shared/.cursor/skills/`, `shared/.cursor/plugins/`, plus any dependent shared docs, scripts, templates, or rules.
   - **Devin:** Check `shared/.devin/skills/` and `shared/.devin/config.json`, plus environment-specific `.devin/skills/` and `.devin/config.json`.
   - **Antigravity:** Check `shared/.agents/skills/`, `shared/.agents/rules/`, plus environment-specific `.agents/skills/` and `.agents/rules/`.
   - Check the same paths under the matching environment folder.
   - Compare against the target repo's `.cursor/`, `.devin/`, `.agents/`, `docs/`, `scripts/`, and `templates/` as applicable.
   - For each paired path, compare modification times per **Modification times** above and note which side is newer before editing.

4. Copy and update relevant items:
   - Create target directories only when needed.
   - Apply **Modification times** for every file: copy missing files from `shared/` first, then from the environment folder; update target files only when the reference copy is newer.
   - Copy Cursor tooling to the target's `.cursor/`, Devin tooling to `.devin/`, and Antigravity tooling to `.agents/`.
   - Preserve project-specific placeholders and filled-in values when the target file is newer or when merging.

5. Verify:
   - Re-read copied or merged files.
   - Run a read-only status/diff check to summarize what changed.
   - Do not build or deploy for tooling-only changes.

## Output

When done, show:
- Target repo and detected environment
- Cursor shared and environment tooling added or already present
- Devin shared and environment tooling added or already present
- Antigravity shared and environment tooling added or already present
- MCP notes
- Any skipped files, conflicts, or placeholders that need user input
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall