magallon
- 4 skills
- 0 followers
- 12 hours ago last updated
- ▌ Refactoring Audit · magallon bundlePerforms a comprehensive 3-phase refactoring audit on any web project, analyzing structure, code quality, and security. Produces a consolidated diagnostic report with severity-rated findings. Use this skill when the user asks to audit a codebase for refactoring opportunities, evaluate technical debt, review code quality, find dead code, detect security issues in server-side logic, or assess overall project health. Triggers on phrases like "audit my code", "find technical debt", "code review the project", "what needs refactoring", "analyze code quality", "find dead code", "check for security issues", or any request to systematically evaluate a codebase before refactoring. This is a read-only diagnostic — it does not modify any files.
- ▌ Refactoring Execute · magallon bundleGenerates a prioritized refactoring plan from audit findings and executes code changes incrementally with user confirmation. Use this skill when the user has a refactoring audit report (from refactoring-audit or any structured findings document) and wants to act on it. Also triggers when the user says "execute the refactoring plan", "fix the audit findings", "refactor based on the report", "apply the refactoring recommendations", "start fixing the issues from the audit", or any request to systematically apply code improvements based on a diagnostic report. This skill modifies files — it always presents a plan and waits for explicit user approval before making any changes.
- ▌ E2e Testing · magallon bundleGenerates and manages end-to-end tests for critical user flows in any web project. Covers test design, Page Object Model, selector strategy, wait patterns, auth state reuse, test data management, network mocking, visual regression, accessibility testing, flaky test diagnosis, and CI/CD pipeline configuration. Stack-agnostic — adapts to Playwright, Cypress, Selenium, Laravel Dusk, Capybara, or any browser automation framework. Use this skill when the user asks to write E2E tests, automate browser tests, test user flows end-to-end, fix flaky tests, set up visual regression testing, configure E2E in CI/CD, debug failing E2E tests, or test across multiple browsers. Also triggers when the user mentions Playwright, Cypress, browser testing, smoke tests, critical path testing, or end-to-end test automation. Works with testing-strategy — use testing-strategy first to decide WHAT to test, then this skill to implement the E2E tests.
- ▌ Testing Strategy · magallon bundleAnalyzes any web project and recommends a comprehensive testing strategy: what to test, which test type to use (unit, integration, component, E2E), how to prioritize coverage, and what mocking approach to follow. Can also generate tests based on its recommendations when the user asks. Use this skill when the user asks "what should I test", "create a testing strategy", "what tests does this project need", "analyze test coverage gaps", "which parts of my code need tests", "help me prioritize testing", "review my tests", "generate tests for this module", or any request to plan, evaluate, or create tests for a codebase. Also triggers when the user mentions testing pyramid, test coverage, TDD, test-driven development, or asks about the right type of test for a piece of code.