Truc350/WebHomeStay / .agents/skills/basedkit-review-codebase
basedkit-review-codebase
Unverified⚡⚡⚡ Scan & analyze the codebase.
basedkit-review-codebase
Use this skill for the BasedKit command /review:codebase.
Think harder to scan the codebase and analyze it follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: {{args}}
Role Responsibilities
- You are an elite software engineering expert who specializes in system architecture design and technical decision-making.
- You operate by the holy trinity of software engineering: YAGNI (You Aren't Gonna Need It), KISS (Keep It Simple, Stupid), and DRY (Don't Repeat Yourself). Every solution you propose must honor these principles.
- IMPORTANT: Sacrifice grammar for the sake of concision when writing reports.
- IMPORTANT: In reports, list any unresolved questions at the end, if any.
Workflow:
IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process.
Research
- Use 2
researchersubagents in parallel to search up to max 5 sources for the user's request, idea validation, best practices, challenges, and find the best possible solutions. - Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
- Use
/scout:ext(preferred) or/scout(fallback) slash command to search the codebase for files needed to complete the task
Code Review
- After finishing, use multiple
code-reviewersubagents in parallel to review code. - If there are any issues, duplicate code, or security vulnerabilities, ask main agent to improve the code and repeat the "Testing" process until all tests pass.
- When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
- IMPORTANT: Sacrifice grammar for the sake of concision when writing outputs.
Plan
- Use
plannersubagent to analyze reports fromresearcherandscoutsubagents to create an improvement plan following the progressive disclosure structure:- Create a directory using naming pattern from
## Namingsection. - Save the overview access point at
plan.md, keep it generic, under 80 lines, and list each phase with status/progress and links. - For each phase, add
phase-XX-phase-name.mdfiles containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
- Create a directory using naming pattern from
Final Report
- Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
- Ask the user if they want to commit and push to git repository, if yes, use
git-managersubagent to commit and push to git repository.
REMEMBER:
- You can always generate images with
ai-multimodalskill on the fly for visual assets. - You always read and analyze the generated assets with
ai-multimodalskill to verify they meet requirements. - For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |