القائمة
Use this skill when working with ADE PR workflows including PR tab data, PR checks/comments, queues, rebase resolution, CI fixes, or merge readiness.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Autonomous PR-to-merge loop. Polls CI and review bots, fixes failures, rebases only on real conflicts, and lands the PR on main. Soft cap of 5 normal iterations plus one force-finalize iteration that bypasses review and fixes only CI. Pure loop — it does NOT run /quality or /test; run those first. Full phase logic lives in docs/playbooks/ship-lane.md.
ADE release conductor: detect whether desktop and/or iOS actually changed, bump desktop patch versions, keep iOS marketing versions fixed while bumping build numbers, ship desktop through the GitHub Actions release workflow, and distribute TestFlight builds to all beta users.
Use this skill when an agent needs to inspect or operate ADE itself through the `ade` CLI, including lanes, chats, actions, proof, runtime/socket state, or help/flag discovery.
Use this skill when creating, inspecting, syncing, committing, pushing, archiving, or rebasing ADE lanes and lane worktrees through `ade lanes` and `ade git`.
Use this skill when using ADE's built-in browser pane, shared browser tabs, screenshots, page inspection, or browser context selection through `ade browser`.
Prove the new code works: enforce the logging/PostHog ground truth, prune dead tests, consolidate fragments, add only tests that prove new contracts, turn each /quality Blocker/High finding into a named regression test, then run CI-mirrored shards. Also keeps docs/mobile/CLI/TUI parity in lockstep.
استنادا إلى تصنيف SOC المهني
| name | ade-pr-workflows |
| description | Use this skill when working with ADE PR workflows including PR tab data, PR checks/comments, queues, rebase resolution, CI fixes, or merge readiness. |
ade prs list --text
ade prs show <pr-id-or-number-or-url> --text
ade prs checks <pr-id-or-number-or-url> --text
ade prs comments <pr-id-or-number-or-url> --text
Use ade help prs and ade help git rebase before guessing PR or rebase flags.
When you create or adopt a GitHub PR, include two links in your final handoff:
githubUrl / html_url.adeUrl printed by ade prs create; if you created or
adopted the PR through another path, run ade link pr <owner/repo> <number> --no-clipboard and include the printed https://ade-app.dev/open?... URL.Prefer the HTTPS ADE link in chat, PR comments, and terminal output because it
unfurls and upgrades into ade://pr/<owner>/<repo>/<number> on machines with
ADE installed. The PR body already gets an automatic "Open in ADE" footer, but
the final agent message should still include both links so the user can jump
straight to either GitHub or the ADE PRs tab.
ade actions list --domain pr --text
ade actions run <domain.action> --input-json '{"key":"value"}'
Before treating a PR as merge-ready, verify working tree cleanliness, pushed branch status, required checks, unresolved review threads, and whether rebasing/merging main introduced conflicts or semantic drift.