Results for “refactoring”

Google TypeScript Style Guide reference for writing, reviewing, and refactoring TypeScript code. Use this skill whenever you are writing TypeScript code, reviewing TypeScript code, refactoring TypeScript, configuring ESLint or linter rules for TypeScript, or when the user asks about TypeScript coding conventions, naming conventions, type system best practices, or import/export patterns. Also trigger when the user mentions 'Google style', 'gts', 'TypeScript style guide', or asks 'how should I name this', 'should I use interface or type', 'how to handle null/undefined' in a TypeScript context. TypeScriptを書く・レビューする・リファクタリングする、ESLintの設定をする、「命名規則」「型の使い方」「import/exportのルール」「interfaceとtypeどっち」「anyを使っていい？」「nullチェックどうする」「Google式」「コーディング規約」「スタイルガイド」などの質問にも対応します。TypeScriptのコードに関する質問や作業であれば積極的にこのスキルを使ってください。

The English summary is being prepared. Showing the original description.

Use when working with code refactoring context restore

The English summary is being prepared. Showing the original description.

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

The English summary is being prepared. Showing the original description.

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...

The English summary is being prepared. Showing the original description.

Use when working with code refactoring context restore

The English summary is being prepared. Showing the original description.

Write clean, readable, and maintainable code following principles from Robert C. Martin's "Clean Code" and Object Calisthenics. Use when writing, reviewing, or refactoring code to improve naming, function design, formatting, error handling, and class structure. Includes code smell detection and refactoring guidance.

The English summary is being prepared. Showing the original description.

two-stage review (spec compliance first, then code quality), refactoring, and quality improvement. Use when reviewing code, eliminating code smells, reducing technical debt, refactoring methods, running self-critique loops, or improving maintainability and readability.

The English summary is being prepared. Showing the original description.

Expert en design patterns (GoF, SOLID, enterprise patterns, refactoring, anti-patterns)

The English summary is being prepared. Showing the original description.

Design patterns v3 — GoF, SOLID, enterprise patterns, anti-patterns, refactoring, language-specific

The English summary is being prepared. Showing the original description.

Guide for building and refactoring a FastAPI + Prefect + PostgreSQL/pgvector analytics pipeline that extracts insights from chat data using LLM classification, embeddings, UMAP/HDBSCAN clustering, and narrative generation. Use this skill whenever working on this project's codebase — including adding features, refactoring, debugging, creating new endpoints, modifying pipeline stages, or reviewing architecture decisions. Also trigger when the user asks about project structure, stack decisions, async migration, or best practices for this specific system.

The English summary is being prepared. Showing the original description.

Improve code structure, readability, and maintainability without changing external behavior through systematic refactoring techniques like extracting functions, removing duplication, simplifying conditionals, and applying design patterns. Use when reducing technical debt, extracting functions or classes, removing code duplication, simplifying complex conditionals, renaming for clarity, applying design patterns, improving code organization, reducing coupling, increasing cohesion, or maintaining test coverage during structural improvements.

The English summary is being prepared. Showing the original description.

Implement test-driven development (TDD) workflow using the red-green-refactor cycle. Use when writing new features, fixing bugs, or refactoring existing code. Always write the failing test first, then implement minimal code to pass, then refactor. Essential for ensuring code reliability, preventing regressions, improving design through testability requirements, documenting expected behavior through tests, enabling confident refactoring, and maintaining high code quality standards throughout the development process.

The English summary is being prepared. Showing the original description.

Refactoring using Remove Parameter in Java Language

The English summary is being prepared. Showing the original description.

Refactoring using Extract Methods in Java Language

The English summary is being prepared. Showing the original description.

Guide for Private and Internal member testing strategies. Use when you need to test private or internal members, configure InternalsVisibleTo, or evaluate testability design. Covers design-first thinking, reflection testing, strategy pattern refactoring, AbstractLogger pattern, and decision frameworks. Keywords: private method testing, internal testing, InternalsVisibleTo, reflection testing, GetMethod BindingFlags, Meziantou.MSBuild.InternalsVisibleTo, testability design, strategy pattern refactoring, testability

The English summary is being prepared. Showing the original description.

Symbol-level refactoring with automatic reference updates using Serena MCP

The English summary is being prepared. Showing the original description.

Code implementation, refactoring, and bugfixes for create-vue-dsfr. Use for implementing features, refactoring code, or fixing bugs. Read the shared project skill before acting.

The English summary is being prepared. Showing the original description.

Code implementation, refactoring, and bugfixes. USE FOR: implementing features; refactoring code; fixing bugs; modifying existing code. DO NOT USE FOR: writing tests (separate skill); documentation (separate skill); commit conventions (separate skill).

The English summary is being prepared. Showing the original description.

Bundle a question and selected project files for a second AI model to review code, investigate bugs, or assess design options. Preview the files and token usage before running through an API or browser.

• Getting a second AI opinion on code
• Investigating errors with relevant project files
• Comparing design and refactoring options

Requests a code review from a separate agent after implementation or before merging. It provides the change summary, requirements, and commit range, then guides follow-up work according to the severity of the findings.

• Reviewing a major feature after implementation
• Checking changes before merging
• Getting another perspective on a complex bug fix

Guides feature development and bug fixes by writing tests before implementation. It confirms each test fails for the expected reason, adds only enough code to pass, and checks the full test suite before completion.

• Implementing a new feature from tests
• Reproducing a bug in a test before fixing it
• Refactoring while keeping tests passing

Verify completed code changes in six stages: build, type checks, lint, tests with coverage, searches for possible secrets, and diff review. Produces a pass/fail report with issues to fix and readiness for a pull request.

• Verifying code after completing a feature
• Checking for problems after refactoring
• Reviewing readiness before creating a pull request

Verify Spring Boot changes through builds, static analysis that checks code without running it, tests, coverage checks, and security scans. Review the diff and produce a pass/fail report showing readiness and issues to fix.

• Checking a Spring Boot service before opening a pull request
• Verifying changes after refactoring or dependency upgrades
• Checking test coverage against the target

Turn a multi-step plan into ready-to-paste ECC slash commands, text commands entered with a slash. Each generated command includes its step identifier, task scope, and acceptance criteria. Steps that cannot carry their scope are marked as blocked for manual handling.

• Turning an implementation plan into commands for each step
• Choosing commands for feature additions, fixes, and refactoring
• Generating commands for a selected step or range