MoonshotAI / MoonshotAI/kimi-code
Research: Inventory current repository structure
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
Question
Perform a complete inventory of the current repository structure to inform the restructuring. Run git ls-files and sort by intent, not by extension:
- What ships (source code that becomes the deliverable)?
- What explains (documentation)?
- What proves (tests and evidence)?
- What is derived (build output, generated files)?
- What is superseded (old plans, closed campaigns, previous designs)?
This research will inform all other tickets.
Label: wayfinder:research
Part of #2517
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run git ls-files in the repository and inventory every tracked path by intent: what ships, explains, proves, is derived, or is superseded. The work is done when the complete categorized inventory is recorded to inform the restructuring tickets in #2517.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- cli, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100