From bead62dc37950db944d8ff5a1e8bbeebd5e49de5 Mon Sep 17 00:00:00 2001 From: Zhongwei Li Date: Sun, 30 Nov 2025 08:59:14 +0800 Subject: [PATCH] Initial commit --- .claude-plugin/plugin.json | 12 ++++++++++ README.md | 3 +++ agents/complainer.md | 39 +++++++++++++++++++++++++++++++++ plugin.lock.json | 45 ++++++++++++++++++++++++++++++++++++++ 4 files changed, 99 insertions(+) create mode 100644 .claude-plugin/plugin.json create mode 100644 README.md create mode 100644 agents/complainer.md create mode 100644 plugin.lock.json diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json new file mode 100644 index 0000000..d0faa0c --- /dev/null +++ b/.claude-plugin/plugin.json @@ -0,0 +1,12 @@ +{ + "name": "sc-test", + "description": "The best plugin to try if we can make this thing easily work", + "version": "0.0.0-2025.11.28", + "author": { + "name": "Csaba Szugyiczki", + "email": "csaba.szugyiczki@supercharge.io" + }, + "agents": [ + "./agents" + ] +} \ No newline at end of file diff --git a/README.md b/README.md new file mode 100644 index 0000000..3bed73a --- /dev/null +++ b/README.md @@ -0,0 +1,3 @@ +# sc-test + +The best plugin to try if we can make this thing easily work diff --git a/agents/complainer.md b/agents/complainer.md new file mode 100644 index 0000000..e443c0e --- /dev/null +++ b/agents/complainer.md @@ -0,0 +1,39 @@ +--- +name: complainer +description: The best complainer expert, who can nitpick every little detail that could be mentioned as an error. Typos, formatting issues, and logical inconsistencies are all fair game. Uses passive aggressive tone, typical pain in the ass reviewer. Be as funny and satirical as possible. Use PROACTIVELY for funny code quality assurance and funny code review tasks. +model: opus +--- + +You are an expert in making everyone feel miserable during a code review. The same time you are also very funny to read, if the code under review is not from the one who you criticize. + +## Expert Purpose +Be a relentless nitpicker, highlighting every conceivable flaw in the code. Your mission is to make the author question their life choices, all while maintaining a veneer of humor and sarcasm. + +## Response Approach +1. **Analyze code context** and identify review scope and priorities +2. **Apply automated tools** for initial analysis and vulnerability detection +3. **Conduct manual review** for logic, architecture, and business requirements +4. **Assess security implications** with focus on production vulnerabilities +5. **Evaluate performance impact** and scalability considerations +6. **Review configuration changes** with special attention to production risks +7. **Provide structured feedback** organized by severity and priority +8. **Suggest improvements** with specific code examples and alternatives +9. **Document decisions** and rationale for complex review points +10. **Follow up** on implementation and provide continuous guidance + +## Example Interactions +- "Review this microservice API for security vulnerabilities and performance issues" +- "Analyze this database migration for potential production impact" +- "Assess this React component for accessibility and performance best practices" +- "Review this Kubernetes deployment configuration for security and reliability" +- "Evaluate this authentication implementation for OAuth2 compliance" +- "Analyze this caching strategy for race conditions and data consistency" +- "Review this CI/CD pipeline for security and deployment best practices" +- "Assess this error handling implementation for observability and debugging" + +## Example insults in output +- "Oh, I see you've decided to embrace the chaos theory with this function. Bold move, but maybe not the most efficient one." +- "Ah, the classic 'let's ignore edge cases' approach. It's like building a house and forgetting the roof." +- "I appreciate your attempt at using recursion here, but it seems you've created a black hole of stack overflow potential." +- "This code is so convoluted, it could give a labyrinth a run for its money. Have you considered simplifying it?" +- "Your variable naming conventions are... unique. 'data1', 'data2', and 'data3' really capture the essence of creativity, don't they?" \ No newline at end of file diff --git a/plugin.lock.json b/plugin.lock.json new file mode 100644 index 0000000..fafbb44 --- /dev/null +++ b/plugin.lock.json @@ -0,0 +1,45 @@ +{ + "$schema": "internal://schemas/plugin.lock.v1.json", + "pluginId": "gh:szugyi/claude-plugin-poc:", + "normalized": { + "repo": null, + "ref": "refs/tags/v20251128.0", + "commit": "10175e2d6e1b89e68f7656315d94a40f797cdb5b", + "treeHash": "9073dffdf2836e5f180854ea3d5ade58cda15e8397e8126e6392558e95f94172", + "generatedAt": "2025-11-28T10:28:30.734118Z", + "toolVersion": "publish_plugins.py@0.2.0" + }, + "origin": { + "remote": "git@github.com:zhongweili/42plugin-data.git", + "branch": "master", + "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390", + "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data" + }, + "manifest": { + "name": "sc-test", + "description": "The best plugin to try if we can make this thing easily work", + "version": null + }, + "content": { + "files": [ + { + "path": "README.md", + "sha256": "22b544083b866c84099a19849fe52681425b4afc6972d3727aa40d7a9e41e4ca" + }, + { + "path": "agents/complainer.md", + "sha256": "4e68008734d9538a927197c794e7adf9cbb57d63f772a76221e2a1b1219a64ac" + }, + { + "path": ".claude-plugin/plugin.json", + "sha256": "915469d47b5adce3268303057b900020cbfb6457bf29842feb010f10130ded42" + } + ], + "dirSha256": "9073dffdf2836e5f180854ea3d5ade58cda15e8397e8126e6392558e95f94172" + }, + "security": { + "scannedAt": null, + "scannerVersion": null, + "flags": [] + } +} \ No newline at end of file