name	developer_review
display_name	Developer Review
icon	rule
description	Code-review workflow for Developer Studio repositories.
enabled_by_default	false
version	1.0
tools	["developer"]
tags	["developer","review"]
author	Thoth

Developer Review

Use this skill when the user asks for a code review, PR review, or risk assessment in Developer Studio.

Prioritize findings over summaries:

Inspect workspace identity, branch, dirty state, and changed files.
Read relevant diffs and implementation files.
Look for correctness bugs, regressions, data loss, security issues, concurrency hazards, and missing tests.
Run or recommend focused tests where useful.
Report findings first with file paths and line references when possible. If no issues are found, say so clearly and mention residual risk.

Do not rewrite code during a review unless the user asks for fixes.

Más de este repositorio

mismo repositorio

Perform multi-source research on a topic and produce a structured report.

Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.

Guidance for querying and managing Thoth's own configuration and logs.

Capture unstructured thoughts and organize them into structured notes saved to memory.

Analyses datasets with professional rigour — statistical summaries, clear narratives, and well-chosen visualisations.

Structured workflow for creating professional designs — slide decks, documents, landing pages, app mockups, and motion storyboards.

name	developer_review
display_name	Developer Review
icon	rule
description	Code-review workflow for Developer Studio repositories.
enabled_by_default	false
version	1.0
tools	["developer"]
tags	["developer","review"]
author	Thoth

Use this skill when the user asks for a code review, PR review, or risk assessment in Developer Studio.

Prioritize findings over summaries:

Inspect workspace identity, branch, dirty state, and changed files.
Read relevant diffs and implementation files.
Look for correctness bugs, regressions, data loss, security issues, concurrency hazards, and missing tests.
Run or recommend focused tests where useful.
Report findings first with file paths and line references when possible. If no issues are found, say so clearly and mention residual risk.

Do not rewrite code during a review unless the user asks for fixes.