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
affaan-m/ECC☆ 284.9KUpdated Oct 20, 2026
Write, review, and refactor Kotlin code using established conventions. Covers safe handling of missing values, immutable data, coroutines for asynchronous work, and type-safe configuration builders, helping keep application code readable and maintainable.
- Reviewing Kotlin code for unsafe null handling
- Refactoring mutable data and deeply nested code
- Designing asynchronous work with coroutines and Flow
affaan-m/ECC☆ 284.9KUpdated Oct 20, 2026
Coordinate feature work, bug fixes, refactoring, and MVP development through shared phases scaled to the change. Related operation skills use this workflow to delegate research, planning, test-first implementation, review, and commits with human approval checkpoints.
- Using a shared process for feature additions and bug fixes
- Scaling development steps to the size of a change
- Organizing MVP development from a design document
affaan-m/ECC☆ 284.9KUpdated Oct 20, 2026
Design or refactor services so business rules stay separate from databases, APIs, and frameworks. Uses Ports and Adapters—interfaces and their implementations—to define clear boundaries, test workflows, and migrate existing code one feature at a time.
- Separating business rules from database and API calls
- Sharing application workflows across HTTP, CLI, and workers
- Replacing infrastructure while preserving business rules
affaan-m/ECC☆ 284.9KUpdated Oct 20, 2026
Write, review, and refactor C# and .NET code using practical conventions for asynchronous work, configuration, and dependency injection—passing services into classes. Includes examples for data access and APIs to support maintainable applications.
- Reviewing C# implementation conventions
- Improving asynchronous code and cancellation handling
- Organizing service dependencies and configuration
affaan-m/ECC☆ 284.9KUpdated Oct 20, 2026
Review and refine code using shared conventions for clear names, readability, error handling, and updates that preserve original data. Identify duplication, oversized functions, and unnecessary complexity to make code easier to understand and maintain.
- Reviewing names and readability in existing code
- Refactoring long functions and deeply nested logic
- Standardizing coding conventions for a new module
affaan-m/ECC☆ 284.9KUpdated Oct 20, 2026
Guide development through test-driven development (TDD): write a test, confirm it fails, add minimal code, then clean up. Apply this cycle to features and bug fixes while checking that existing behavior still passes its tests.
- Adding features with tests written first
- Reproducing a bug in a test before fixing it
- Refactoring while keeping tests passing
NousResearch/hermes-agent☆ 255.6KUpdated Oct 20, 2026
Coordinate large migrations, reviews, or research tasks across multiple agents. Keep plans and intermediate results in scripts and files, challenge findings with independent checks, and integrate verified work in controlled batches.
- Splitting large file migrations across agents
- Testing audit findings against counter-evidence
- Cross-checking research from different perspectives
NousResearch/hermes-agent☆ 255.6KUpdated Oct 20, 2026
Guide coding tasks toward the smallest complete change by reusing existing code, platform features, and installed dependencies. Address affected callers and necessary checks, then explain skipped work, unchecked areas, and risks in a brief reply.
- Build a minimal version that meets the request
- Fix a root cause in shared code
- Refactor while limiting unnecessary additions
DietrichGebert/ponytail☆ 169.6KUpdated Oct 18, 2026
Restructure code through extraction, consolidation, or responsibility moves while preserving its behavior. Establish checks before editing, repeat them afterward, and keep intermediate versions buildable and testable without mixing in feature changes.
- Extracting code while preserving behavior
- Consolidating duplicate processing
- Moving responsibilities between modules
JuliusBrussee/caveman☆ 113.9KUpdated Oct 19, 2026
Connect agent tasks into a sequence where each step receives the previous output. Use custom prompts or predefined workflows to analyze code, plan refactoring, generate tests, optimize performance, or transform data through multiple stages.
- Turn code analysis into an improvement plan
- Prioritize and refactor existing code
- Find test gaps and generate unit tests
ruvnet/RuView☆ 98.9KUpdated Oct 20, 2026
Work with AI as a coding partner, choosing who writes code and who guides the work. Supports role switching, test generation, ongoing code review, debugging, and step-by-step explanations for learning.
- Write code with ongoing AI review
- Direct AI implementation while reviewing its output
- Develop features by writing tests first
ruvnet/RuView☆ 98.9KUpdated Oct 20, 2026
Audit a codebase for unnecessary complexity, including dead code, duplicated state, redundant interfaces, and obsolete compatibility paths. Receive evidence-backed simplification candidates, or authorize changes that remove justified targets and validate the behavior that must remain.
- Finding code that can be safely removed
- Consolidating duplicated state or APIs
- Reviewing obsolete compatibility paths and design records
tt-a1i/archify☆ 86.5KUpdated Oct 20, 2026
Simplify Rust code in RTK by replacing verbose loops, unnecessary copies, and excessive abstractions with common Rust patterns. Preserve behavior and project requirements, including error context, fallback handling, exit codes, and existing test modules.
- Simplifying verbose loops and string construction
- Removing unnecessary string copies
- Reducing nested conditional and error handling code
rtk-ai/rtk☆ 84.1KUpdated Oct 20, 2026
Guide Rust development through test-driven development: write a failing test, implement enough code to pass, then refactor. Includes practical test patterns and final checks for formatting, static analysis, and test results.
- Adding Rust features with tests first
- Reproducing bugs with failing tests before fixing them
- Testing invalid inputs and error paths
rtk-ai/rtk☆ 84.1KUpdated Oct 20, 2026
Choose Rust design patterns for RTK modules that process command output. Use concrete examples to structure configuration, prevent type mixups, manage parser states, and select abstractions suited to the task without adding unnecessary architectural complexity.
- Planning the structure of a new command output filter
- Preventing mixups between values with the same underlying type
- Organizing configuration with many optional fields
rtk-ai/rtk☆ 84.1KUpdated Oct 20, 2026
Keep coding changes small by questioning unnecessary work and reusing existing code, standard libraries, and native platform features. Apply this approach to implementation, bug fixes, reviews, and dependency choices while preserving validation, security, and accessibility.
- Reduce unnecessary code and dependencies
- Fix shared root causes of bugs
- Review code for excessive abstraction
diegosouzapw/OmniRoute☆ 79KUpdated Oct 20, 2026
Breaks complex goals into actionable tasks, plans their order, and coordinates execution across agents. It tracks progress, adjusts priorities and dependencies, and combines separate outputs into a consistent deliverable.
- Coordinate development of a multi-part authentication system
- Manage payment module work from analysis through testing
- Run tests and documentation updates in parallel
ruvnet/ruflo☆ 77.8KUpdated Oct 20, 2026
Assembles teams of AI agents by analyzing task complexity, required skills, and resource needs. It covers selecting specialists, adjusting team size to workload, and refining coordination using patterns from past executions.
- Assemble specialists for payment system refactoring
- Scale agents to process large batches of data files
- Find networking specialists for WebSocket debugging
ruvnet/ruflo☆ 77.8KUpdated Oct 20, 2026
Turn specifications and designs into working code using test-driven development: write failing tests, implement enough code to pass, then refactor. The workflow also covers error handling, performance improvements, documentation, and coordinated changes across components.
- Implementing a feature from specifications and designs
- Developing authentication or APIs with tests
- Refactoring code while checking test results
ruvnet/ruflo☆ 77.8KUpdated Oct 20, 2026
Coordinate groups of AI agents across multiple GitHub repositories. Analyze dependencies, organize shared updates and refactoring, run tests, and create linked pull requests so related projects can be changed together.
- Updating dependencies across multiple repositories
- Coordinating shared API and library changes
- Applying security patches across projects
ruvnet/ruflo☆ 77.8KUpdated Oct 20, 2026
Set up a coordinated team of three or more AI agents for development tasks spanning multiple files. Configure the team structure, assign specialized roles, and prepare parallel work with named agents and messaging.
- Implementing a feature across multiple files
- Refactoring across modules with coordinated agents
- Sharing a security audit across an agent team
ruvnet/ruflo☆ 77.8KUpdated Oct 20, 2026
Coordinate changes across multiple GitHub repositories, align package versions, synchronize documentation, and run integration tests. The skill also guides shared repository templates and organizes AI agents to handle related development tasks.
- Aligning dependency versions across repositories
- Updating projects that use a shared library
- Standardizing documentation and CI workflows
ruvnet/ruflo☆ 77.8KUpdated Oct 20, 2026
Organize software development from requirements and design through testing, review, and deployment. Uses Claude Flow to coordinate specialized agents, share decisions across sessions, and guide implementation with tests written before code.
- Developing a feature from requirements through review
- Refactoring legacy code with supporting tests
- Investigating bugs and adding regression tests
ruvnet/ruflo☆ 77.8KUpdated Oct 20, 2026