ワンクリックでManusで任意のスキルを実行

始める

run-sync-check

スター11

フォーク3

更新日2026年5月13日 15:04

Run agnostic-ai sync --check, interpret the diff, and pick the right next step. Use after editing specs or adapters.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Chemaclass

Chemaclass/agnostic-ai

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

run-sync-check

Verifies that emitted target files match what the current specs would produce.

Steps

Build the binary if changed: make build.
Run ./agnostic-ai sync --check. Exit 0 means the working tree matches the bundle.
If exit is non-zero, the tool prints a unified diff per drifting file.
Decide:
- Source edited, emitted file lags -> run agnostic-ai sync to refresh.
- Adapter edited, emitted files would change -> intentional. Run agnostic-ai sync and review the diff in git diff.
- Neither edited but check still drifts -> capture mode skipped reading existing files. Re-run with agnostic-ai sync and inspect.
Never edit emitted files by hand to silence the check. The next sync rewrites them.

CI

sync --check is the gate. A drift exits 1 and fails the workflow. The fix is always to re-sync locally and commit, never to edit the emitted file.

このリポジトリの他の Skills

同じリポジトリ

cut-release

Chemaclass/agnostic-ai

Cut a new agnostic-ai release end to end. Use when the user wants to ship a new version (tag + GitHub Release).

2026-06-1611

gh-issue

Chemaclass/agnostic-ai

Fetch a GitHub issue, create a branch, implement with TDD, and open a PR

2026-06-1611

gh-issues

Chemaclass/agnostic-ai

Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the gh-issue skill, sequentially.

2026-06-1611

sample-skill

Chemaclass/agnostic-ai

A sample skill for golden snapshot tests.

2026-06-0511

dos

Chemaclass/agnostic-ai

dos

2026-06-0311

tres

Chemaclass/agnostic-ai

tres

2026-06-0311

name	run-sync-check
description	Run agnostic-ai sync --check, interpret the diff, and pick the right next step. Use after editing specs or adapters.

run-sync-check

Verifies that emitted target files match what the current specs would produce.

Steps

Build the binary if changed: make build.
Run ./agnostic-ai sync --check. Exit 0 means the working tree matches the bundle.
If exit is non-zero, the tool prints a unified diff per drifting file.
Decide:
- Source edited, emitted file lags -> run agnostic-ai sync to refresh.
- Adapter edited, emitted files would change -> intentional. Run agnostic-ai sync and review the diff in git diff.
- Neither edited but check still drifts -> capture mode skipped reading existing files. Re-run with agnostic-ai sync and inspect.
Never edit emitted files by hand to silence the check. The next sync rewrites them.

CI

sync --check is the gate. A drift exits 1 and fails the workflow. The fix is always to re-sync locally and commit, never to edit the emitted file.