feat: add Warp (Oz) integration via skill

[ComputelessComputer]

Summary

Add RTK support for Warp's Oz agent using the skill system.

Warp doesn't have pre-execution hooks like Claude Code (PreToolUse) or OpenCode (tool.execute.before), so this uses an instruction-based approach: a SKILL.md file that tells the agent to always prefix commands with rtk.

What's included

File	Purpose
warp/skills/rtk/SKILL.md	Warp skill with golden rule, full command reference, and verification steps
warp/README.md	Setup guide (global + per-project), comparison with hook-based integrations

Setup

# Global:
mkdir -p ~/.agents/skills/rtk
cp warp/skills/rtk/SKILL.md ~/.agents/skills/rtk/SKILL.md

# Per-project:
mkdir -p .agents/skills/rtk
cp warp/skills/rtk/SKILL.md .agents/skills/rtk/SKILL.md

The skill is auto-discovered by Warp from any of its supported skill directories (.agents/skills/, .warp/skills/, .claude/skills/, etc.).

Co-Authored-By: Oz oz-agent@warp.dev

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

ComputelessComputer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[pszymkowiak]

Hi! Two things needed before we can review:

1. Retarget to develop — this PR targets master, but all PRs should target develop. You can change the base branch in the PR settings (right sidebar).
2. Sign the CLA — if not already done, please sign at https://cla-assistant.io/rtk-ai/rtk

Thanks!

[aeppling]

Hey

We are cleaning up the codebase and improving the project structure for better onboarding. As part of this effort, PR #826 reorganizes src/ from a flat layout into subfolders.

No logic changes — only file moves and import path updates.

What you need to do

Rebase your branch on develop when receiving this comment:

git fetch origin && git rebase origin/develop

Git detects renames automatically. If you get import conflicts, update the paths:

use crate::git;        // now: use crate::cmds::git::git;
use crate::tracking;   // now: use crate::core::tracking;
use crate::config;     // now: use crate::core::config;
use crate::init;       // now: use crate::hooks::init;
use crate::gain;       // now: use crate::analytics::gain;

Need help rebasing? Tag @aeppling