Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.
About the project
Apache ShardingSphere is a database enhancement layer that makes heterogeneous databases easier to access and govern as a unified system, without replacing the underlying databases. It supports distributed database capabilities such as sharding, read-write splitting, SQL federation, encryption, masking, auditing, and traffic control for enterprise data architectures.
Used to analyze Apache ShardingSphere community issues. Emphasizes root-cause-first and evidence-first classification before conclusions, and produces copy-ready GitHub issue replies in the voice of an Apache ShardingSphere community maintainer.
Implement, fix, refactor, or remove repository code under required scope, non-regression, verification, and review gates. Use whenever a task may change a production, test, script, or other implementation artifact, including build logic, generated source, and behavior-affecting configuration. Also use it alongside a…
Apply Apache ShardingSphere's written coding standards during implementation, fixes, refactoring, and code review, or perform a standalone read-only compliance audit of a user-specified scope. Uses CODEOFCONDUCT.md, applicable AGENTS.md rules, Checkstyle, Spotless, and other repository-defined standards, including…
Generate standard unit tests for one or more target classes in Apache ShardingSphere; by default, target 100% class/line/branch coverage and pass quality gates; perform explicit merge analysis, suitability filtering, and refactor optimization for parameterized tests.
Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence. Use for code-correctness or mergeability decisions, CI-focused review, root-cause and regression analysis, complete consolidated findings, copy-ready committer feedback, challenged…
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: