ReddRadar
Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/product/removing-a-feature-of-a-microservice
SKILL.md
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?