logic-review
SolidReview chapter drafts for paragraph-level flow, transitions, and argument continuity before editing.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- yha9806
- Repository
- yha9806/academic-writing-toolkit
- Created
- 4 months ago
- Last Updated
- 4 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
review-logic
Use when: reviewing code for logic correctness, algorithmic bugs, missing error handling, async/await mistakes, null/undefined risks, race conditions, type contract violations, or spec compliance. Dispatched by review-orchestrator for --frontend, --backend, and --all. Also invoked directly: "review logic", "check correctness", "are there any bugs here". NOT for: security vulnerabilities, performance profiling, style/naming preferences, or architectural pattern concerns — those belong in their respective specialized reviewers.
go-logic-review
Review Go code for business logic correctness, boundary conditions, off-by-one errors, state management, data flow integrity, and return value contracts. Trigger on any Go code change that modifies behavior, conditional logic, state transitions, or data processing. Use for logic-correctness focused review.
doc-review
Reviews a document against a fixed checklist before it is published or shared -- clarity, undefined terms, unenforced rules, undated decisions, missing owners, contradictions, and content that is stale on its face. Use when the user says "review this doc", "is this page clear", "check this page before I publish", "does this make sense to someone outside the team", or pastes a document/link and asks for a check before sending it out. Read-only -- this skill reports findings, it never edits or rewrites the document. Not for a message or reply (that is /daikenja:compose) or a pre-send substance check on a draft message (that is /daikenja:preflight) -- this skill is for standalone documents (specs, runbooks, wikis, READMEs), not chat replies.