Pit : Feature Requests

[BIJJUDAMA]

Have a Feature Idea?

I am currently looking for suggestions to make Pit better. If you have an idea for a new command or a performance optimization, Comment below and I will create a issue regarding that for you

Submission Requirements

To keep the project organized, every issue must include two parts:

1. The Context: A clear explanation of the feature or the bug.
2. The Implementation Plan: A brief outline of how you plan to fix it or how the logic should be structured.

Implementation Plan

Explain the logic

• Which files in pit-project/ need to be modified/created?
• How does this interact with the .pit/index?
• What new helper functions in utils/ will be needed?

Also add the header file if you are suggesting a new feature

1.  **The Command:** The exact CLI signature.
2.  **What it does:** A high-level description of user-facing behavior.
3.  **How it does:** A technical breakdown of interactions with `.pit/` and the filesystem.
4.  **What data structure it uses:** Explicit mention of the Data Structures (Lists, Dicts, Sets, Trees) and the rationale for their choice.

[masampaiosp]

I’d like to suggest introducing a lightweight Feature Proposal Framework to standardize how new ideas are described (problem, command, behavior, technical interaction, data structures, and phased scope). This could help keep discussions organized and make prioritization and review easier before implementation..

[BIJJUDAMA]

@masampaiosp What kinda of frameworks do you think would be good to use?