sync-tasks
Warm the task graph and vector store by synchronizing a configured task board through the reviewer MCP server. Use when the user asks to sync or index board tasks.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- sync-tasks
- description
- Warm the task graph and vector store by synchronizing a configured task board through the reviewer MCP server. Use when the user asks to sync or index board tasks.
03 SKILL.md 正文
Sync Tasks
Reply in Russian. This is a thin, server-side trigger: the server enumerates, normalizes, and indexes the board. Do not enumerate tasks in the client and do not send credentials.
-
Resolve the repository path with
git rev-parse --show-toplevel, then rungit -C <path> remote get-url origin. For HTTPS and SSH URLs, remove the scheme, userinfo, and host; for scp-style remotes, remove everything through the host's first colon. Preserve every path segment after the host or scp colon, remove the leading slash, strip a trailing.git, then lowercase and validate the result as the canonical lowercase repository id (owner/nameorgroup/.../name). Examples:https://gitlab.example.com/group/sub/repo.git→group/sub/repossh://git@gitlab.example.com/group/sub/repo.git→group/sub/repogit@gitlab.example.com:group/sub/repo.git→group/sub/repo
If origin is missing or ambiguous, ask for the complete namespace/repo id; do not guess from the directory name.
-
Resolve branch independently. Pass a non-null branch only when the user explicitly supplied or selected one and it is in the tracked branches list (
REVIEW_BRANCHES). With no explicit tracked selection, passbranch=nullso the server uses its primary tracked branch. Never infer the branch from the current worktree branch or blindly pass an untracked feature branch. -
Call only repo mode with operation flags. The server owns effective board-policy resolution; do not reconstruct policy in the client:
sync_board(repo=<canonical owner/name or group/.../name>, branch=<explicit tracked branch or null>, limit=<limit or null>, purge_orphaned=<explicit request or false>, keep_with_prs=<explicit request or true>, force_renormalize=<explicit request or false>) -
If the result is a configuration or policy error, explain it in Russian and stop. Do not retry through unfiltered explicit mode: that could enumerate or purge the wrong task corpus.
-
Report the server-side summary in Russian, including
eligible,filtered_by_age,filtered_archived,age_unknown,archive_unknown,filter_applied,filter_fingerprint,filter_source,by_board,purge, andwarnings. Explain warnings and leave the local repository unchanged.
sync_board is idempotent: rerunning is safe and inexpensive when the watermark is warm. It reads
the board; it never writes back.
04 同仓库更多 Skills
migrate-to-e2e
Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for /migrate-to-e2e, "migrate our tests to e2e", "port these Maestro flows", "move our TesterArmy tests", or when a project has an e2e config and an older suite still running.
e2e
Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.
create-verification-skill
Generate a project-local verify-<app> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for /create-verification-skill, "make a verification skill for this repo", or when a project has no scripted way to prove UI behavior.
actera-status
Show the Actera connection, mode, evaluation-failure behavior, whether the hooks run, and report delivery.
deja-search
deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.
deja-reflect
End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.