A read-only investigation of a software codebase, including its modules, dependencies, call paths, configuration, and tests. The report distinguishes direct evidence from conclusions drawn from it.
A systems-code review agent that tracks every changed decision branch from its contract through the evidence needed to trust it. A branch is a path such as an early return, fallback, allow-list check, or null check.
An adversarial review agent that tries to disprove specific software-review findings submitted by another agent. It returns whether each finding was rejected, not proven, or could not be rebutted.
A code-review agent focused only on reliability in unusual situations, including boundary cases, error handling, resource cleanup, concurrency, and exception paths. Its instructions are written in Chinese.
A software-review agent that checks whether code matches the requested features, design documents, tasks, and interface agreements. It focuses on expected behavior and missing requirements.
A project-rules reviewer that checks code against explicitly stated engineering standards, such as naming, file structure, dependencies, logging, and synchronization rules.
A command that invokes a manual self-review mode for the coding agent. It reviews errors corrected in the current conversation and produces structured suggestions.
A guide to designing the overall structure of a software system. It covers how to divide modules, manage dependencies, organize data, and define system interfaces.
A practical guide to writing and reviewing readable, maintainable code. It covers naming, function structure, control flow, comments, and safe handling of resources.
A guide to designing individual software components, such as classes, modules, interfaces, and data models. It includes rules for responsibilities, dependencies, error handling, concurrency, and common design patterns.
A guide to designing systems made of multiple computers or services that communicate over a network. It covers delays, lost connections, security, coordination, data consistency, failures, and recovery.
A feedback process that turns repeated corrections into lasting rules or skill updates. It reviews what went wrong, finds the root cause, and suggests how to prevent the same mistake later.
A C++ coding-standard guide based on the Google C++ Style Guide and limited to C++17.
★not rated 159 7mo agoA40 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: