core/store-pruning

Removes unused Redux selectors, actions, reducers, and saga flows after production-usage verification.

6|6|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/intent-hq/cloudlands-fe --skill core-store-pruning-intent-hq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: core/store-pruning
Source: https://github.com/intent-hq/cloudlands-fe/tree/main/.agents/skills/themis/core/store-pruning
Command: npx skills add https://github.com/intent-hq/cloudlands-fe --skill core-store-pruning-intent-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Redux stores accumulate dead selectors, actions, reducer cases, and saga flows over time, making the codebase harder to navigate and maintain. This Skill provides a disciplined procedure for pruning that dead surface area without accidentally deleting code that still has production consumers or public-boundary obligations. ## Core Features & Use Cases - Unused Selector Removal: Deletes selectors with no production consumer, including test-only references and dead barrel re-exports. - Action Lifecycle Checks: Verifies each action has both a production trigger (dispatch, saga put, IPC bridge) and a production handler (reducer case, saga watcher) before removal. - Saga Flow Pruning: Removes orphaned watchers, workers, request/success/failure actions, and channel bridges tied to dead flows. - Use Case: When asked to clean up a bloated Redux store, the agent searches production code separately from tests, prunes confirmed-dead items, and hands off verifier-ready evidence for every deletion. ## Quick Start Ask the agent to prune unused selectors, actions, and saga flows from the Redux store and provide production-usage evidence for each removal.

Frequently Asked Questions about core/store-pruning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely remove unused Redux selectors and actions?▼

Search production code separately from tests for each selector and action. Remove selectors with no production consumer, and remove actions lacking either a production trigger or a production handler, since test-only references do not keep items alive.

When should Redux store pruning be performed?▼

Only when explicitly requested. Pruning should never run automatically during unrelated feature work, bugfixes, migrations, or cleanup, because it requires dedicated production-usage and public-boundary verification before any deletion.

Does a saga-handled action stay if nothing dispatches it?▼

No. If a saga handles an action with no production trigger, both the action and the saga logic are removed, unless a documented external or public boundary proves the trigger exists outside the repository.

What evidence is needed before deleting store code?▼

Record the production search terms and paths used, the test-only references that did not preserve the item, any external or public boundary checked, and the tests or validation commands run after pruning.

What related dead code gets removed with a pruned action?▼

Removal cascades to orphaned saga watchers, workers, channel bridges, component dispatches, reducer cases, helper functions, tests, fixtures, barrel exports, type aliases, and constants that lose their only production consumer.