removing-a-feature-of-a-microservice
Removes a configuration property, functional endpoint, event source, event sink, web handler endpoint, ticker or metric, from a microservice. Use when explicitly asked by the user to remove a feature of a microservice.
When & Why to Use This Skill
This Claude skill automates the systematic removal of features from microservices, including configuration properties, functional endpoints, event sources, and metrics. It ensures codebase integrity by synchronizing changes across service definitions (service.yaml), Go implementation logic, unit tests, and documentation, significantly reducing the manual effort required for refactoring.
Use Cases
- Feature Deprecation: Efficiently remove outdated or deprecated API endpoints and web handlers to maintain a clean and secure service interface.
- Event-Driven Architecture Cleanup: Safely delete obsolete event sources and sinks while ensuring all related implementation code and custom types are purged.
- Technical Debt Reduction: Identify and remove unused metrics, tickers, and configuration properties to keep the microservice lean and maintainable.
- Automated Workflow Synchronization: Streamline the update of boilerplate code via 'go generate' and refresh local documentation (AGENTS.md) to reflect structural changes.
| name | Removing a Feature of a Microservice |
|---|---|
| description | Removes a configuration property, functional endpoint, event source, event sink, web handler endpoint, ticker or metric, from a microservice. Use when explicitly asked by the user to remove a feature of a microservice. |
Workflow
Copy this checklist and track your progress:
Removing a part of a microservice:
- [ ] Step 1: Remove Definition From service.yaml
- [ ] Step 2: Remove Implementation
- [ ] Step 3: Remove Test
- [ ] Step 4: Remove Unused Custom Types
- [ ] Step 5: Update Boilerplate code
- [ ] Step 6: Document the Microservice
Step 1: Remove Definition From service.yaml
Remove the definition from service.yaml.
Step 2: Remove Implementation
Remove any implementation code from service.go.
Step 3: Remove Test
Remove the corresponding test fom service_test.go.
Step 4: Remove Unused Custom Types
If the deleted definition was using non-primitive custom types that are no longer used elsewhere, remove the definition of the unused types from the API directory.
Step 5: Update Boilerplate Code
Run go generate to update the boilerplate code.
Step 6: Update Documentation
Update the microservice's local AGENTS.md to reflect the removal.