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

regression-dog

スター4

フォーク0

更新日2026年4月5日 18:17

Review code for regressions. TRIGGER when: reviewing changes, checking for breakage, or auditing commits (e.g., "did I break anything", "review last commit").

インストール

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

Manusで実行

ソース

imaman

imaman/skills

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

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

ソフトウェア品質保証アナリスト・テスターコンピュータ・数学職·SOC 15-1253

ファイルエクスプローラー

2 ファイル

SKILL.md

readonly

name	regression-dog
description	Review code for regressions. TRIGGER when: reviewing changes, checking for breakage, or auditing commits (e.g., "did I break anything", "review last commit").

Review code changes for behavioral differences between the before and after code.

Important:

Do NOT run tests, typechecks, linters, or build commands. CI already handles those. Focus your context budget entirely on reasoning about the code changes and its implications on logic/behavior/data/etc.
Enumerate behavioral differences: "this used to do X, now it does Y." Do not judge whether the old or new behavior is correct — just surface the delta. Do not flag pre-existing issues or suggest improvements.

Output format:

List regressions first, numbered, with severity.
After the regressions section, add a "Cleared" section listing items that were reviewed and found to have no issues. Prefix each cleared item with a ✅ emoji.

Scope (pass as arguments):

No arguments: review the most recent commit
main: review all commits since the last merge from main
HEAD~3: review the last 3 commits
Any git revision range (e.g., abc123..HEAD, main..HEAD)

このリポジトリの他の Skills

同じリポジトリ

top-dog

imaman/skills

Orchestrate the review skills (review-dog, regression-dog) into one deduplicated, adjudicated report. TRIGGER when: the user wants a combined/full/aggregated review of a branch or commit (e.g., "run the full review", "review this branch with everything", "give me the aggregated review").

2026-05-274

review-dog

imaman/skills

Review code changes for bugs, style, best practices, and adherence to project conventions.

2026-05-274

bug-dog

imaman/skills

Review new/changed code for bugs. TRIGGER when: checking for bugs, auditing new logic, or validating correctness (e.g., "any bugs here?", "check this for bugs", "is this correct?").

2026-04-114

jsdoc-writer

imaman/skills

Add JSDoc to code entities. TRIGGER when: user asks to add/write/improve JSDoc (e.g., "add jsdoc to Foo", "jsdoc for Bar").

2026-04-034

name	regression-dog
description	Review code for regressions. TRIGGER when: reviewing changes, checking for breakage, or auditing commits (e.g., "did I break anything", "review last commit").

Review code changes for behavioral differences between the before and after code.

Important:

Do NOT run tests, typechecks, linters, or build commands. CI already handles those. Focus your context budget entirely on reasoning about the code changes and its implications on logic/behavior/data/etc.
Enumerate behavioral differences: "this used to do X, now it does Y." Do not judge whether the old or new behavior is correct — just surface the delta. Do not flag pre-existing issues or suggest improvements.

Output format:

List regressions first, numbered, with severity.
After the regressions section, add a "Cleared" section listing items that were reviewed and found to have no issues. Prefix each cleared item with a ✅ emoji.

Scope (pass as arguments):

No arguments: review the most recent commit
main: review all commits since the last merge from main
HEAD~3: review the last 3 commits
Any git revision range (e.g., abc123..HEAD, main..HEAD)