code-analysis

スター5

フォーク3

更新日2026年4月15日 09:21

Code review and analysis workflow

インストール

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

Manusで実行

ソース

Calhooon

Calhooon/dolphinmilk

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

ダウンロード

Manusで実行

Code Analysis Skill

When asked to review or analyze code:

Use file_search to find relevant files
Use file_read to examine source code
Use execute_bash to run linters, tests, or analysis tools
Summarize findings with specific file:line references

Gotchas

Read the file before suggesting changes. Never propose modifications to code you haven't read — context matters for correctness.
Check for existing tests before claiming something is untested. Use file_search to look for test files (test_*.rs, *_test.go, etc.) before concluding test coverage is missing.

このリポジトリの他の Skills

同じリポジトリ

browser

Calhooon/dolphinmilk

Navigate web pages, read content, and interact with elements via headless Chrome.

2026-04-155

fleet

Calhooon/dolphinmilk

Fleet management — spawn, monitor, and coordinate child agents via BRC-33 MessageBox and BRC-52 authorization.

2026-04-155

image-generation

Calhooon/dolphinmilk

AI image generation via x402 micropayment

2026-04-155

messaging

Calhooon/dolphinmilk

Cross-wallet communication via BRC-33 MessageBox

2026-04-155

verification

Calhooon/dolphinmilk

Double-check outputs by re-running queries and comparing results. Use when accuracy is critical or when you suspect an error in a previous tool result.

2026-04-155

wallet

Calhooon/dolphinmilk

Generic bridge to any BRC-100 wallet endpoint via wallet_call. Use for discovery, certificates, HMAC, key linkage, and transaction management — endpoints not covered by existing dedicated wallet tools.

2026-04-155

name	code-analysis
description	Code review and analysis workflow
auto_activate	false
tools	["file_read","file_search","execute_bash"]

Code Analysis Skill

When asked to review or analyze code:

Use file_search to find relevant files
Use file_read to examine source code
Use execute_bash to run linters, tests, or analysis tools
Summarize findings with specific file:line references

Gotchas

Read the file before suggesting changes. Never propose modifications to code you haven't read — context matters for correctness.
Check for existing tests before claiming something is untested. Use file_search to look for test files (test_*.rs, *_test.go, etc.) before concluding test coverage is missing.