feature-miner

Extract atomic features with source evidence into features_raw.json.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Swear4/agent_rules --skill feature-miner-swear4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-miner
Source: https://github.com/Swear4/agent_rules/tree/main/agent-universal/skills/feature-miner
Command: npx skills add https://github.com/Swear4/agent_rules --skill feature-miner-swear4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature Miner analyzes source code file by file to extract atomic functionalities with evidence. It uses a structured, triple-pass cognitive approach to ensure precise discovery after project-mapper.

Core Features & Use Cases

  • Identify cohesive features from a codebase with verifiable proofs sourced from real functions and files.
  • Generate a comprehensive features_raw.json suitable for audits, refactoring, and documentation.
  • Use case: after codebase_map.json is produced, produce a feature inventory for roadmap planning and QA.

Quick Start

Run the feature-miner after project-mapper has produced codebase_map.json and review the resulting features_raw.json.

Frequently Asked Questions about feature-miner

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

FAQPage Schema
How do I extract atomic features from a codebase for audit and planning?

Feature extraction identifies atomic functionalities from source code by attaching verifiable proof from real functions and files. It uses a structured triple-pass approach to generate a features_raw.json inventory of macro-systems, mid-level pépites, and micro-capacities for audit, refactoring, and documentation.

How do I generate a feature inventory with source evidence for refactoring?

You generate a feature inventory by analyzing source code file by file to extract cohesive features with explicit sourceEvidence. This produces a features_raw.json file enforcing strict validation rules, ensuring every extracted feature is grounded in code for accurate refactoring and auditing.

Do I need a codebase map before extracting code features?

Yes, you need a codebase_map.json produced by a project-mapper before extracting code features. Feature extraction operates after codebase_map.json is produced, using the mapped structure to generate the final features_raw.json inventory for roadmap planning and QA.

What is the best way to ensure traceability during code-analysis?

The best way to ensure traceability during code-analysis is to enforce strict validation where extracted features must be grounded in code and include explicit sourceEvidence. This guarantees every macro-system, mid-level pépite, and micro-capacity includes verifiable proof sourced from real functions and files.

Does feature extraction work with a specific codebase structure?

Feature extraction works with any codebase structure as long as codebase_map.json has been produced first. It analyzes source files file by file to identify cohesive atomic features, attaching verifiable proofs from real functions regardless of the underlying project layout or architecture.