Conversation
- Remove 9 IDE/git-specific skills (brainstorming, git worktrees, code review, subagent-driven-development, etc.) - Remove platform plugin configs (.claude-plugin, .cursor-plugin, .codex, .opencode, gemini) - Remove tests, docs, commands, hooks, agents directories - Adapt 5 remaining skills for daemon context: - systematic-debugging: trading-relevant examples (API/exchange debugging) - test-driven-development: Python/pytest examples instead of TS/npm - writing-plans: removed git/worktree refs, simplified for scripts - executing-plans: simplified, removed subagent/git references - verification-before-completion: adapted for script execution context - Update all cross-references (removed superpowers: prefix) - Replace "your human partner" with "the user" throughout - New README explaining what was kept, removed, and adapted Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refines the 'Superpowers' library for integration with GigaBrain SuperAgents. The primary goal is to streamline the skill set, making it highly relevant and efficient for autonomous agent operations by focusing on fundamental development and reasoning processes. The changes ensure that the adapted skills are aligned with the operational context of SuperAgents, promoting systematic debugging, test-driven development, and robust plan execution. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request significantly refactors the Superpowers project, adapting it for GigaBrain SuperAgents and OpenCode. Key changes include removing platform-specific configurations and skills (e.g., for Claude Code, Cursor, Git workflows), simplifying the brainstorm server to use zero-dependency Node.js built-ins, and updating documentation across various files like README.md, RELEASE-NOTES.md, and installation guides. The executing-plans skill has been streamlined, and the systematic-debugging and test-driven-development skills have been updated with Python examples and refined guidance. The visual-companion for brainstorming has been refactored for a non-blocking browser-terminal interaction model, and a document review system has been introduced for specs and plans. A review comment highlights a concern regarding the removal of valuable guidance on 'Integration Tests as Afterthought' and related anti-patterns from testing-anti-patterns.md, suggesting its re-instatement to maintain comprehensive TDD guidance.
|
|
||
| **If you're testing mock behavior, you violated TDD** - you added mocks without watching test fail against real code first. | ||
|
|
||
| ## Quick Reference |
There was a problem hiding this comment.
This file has been simplified, which is good for conciseness. However, the removal of 'Anti-Pattern 5: Integration Tests as Afterthought' and its related sections ('When Mocks Become Too Complex', 'TDD Prevents These Anti-Patterns') is a significant loss of valuable guidance. The principle that testing is an integral part of implementation, not an optional follow-up, is fundamental to TDD. I recommend re-instating this section to maintain the quality of the guidance for the agent. Additionally, the 'Quick Reference' table is missing the 'Over-complex mocks' anti-pattern, which was present before and is valuable.
Summary
systematic-debugging,test-driven-development,writing-plans,executing-plans,verification-before-completionTest plan
skills_manifest.yamllist_skills()shows the 5 new skillsload_skill("systematic-debugging")returns full content🤖 Generated with Claude Code