First off, thanks for taking the time to contribute! 🎉
The following is a set of guidelines for contributing to Claude Analytics. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
This section guides you through submitting a bug report for Claude Analytics. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
- Use a clear and descriptive title for the issue to identify the problem.
- Describe the steps to reproduce the problem in as much detail as possible.
- Include screenshots and animated GIFs which show you following the reproduction steps.
This section guides you through submitting an enhancement suggestion for Claude Analytics, including completely new features and minor improvements to existing functionality.
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as much detail as possible.
- Explain why this enhancement would be useful to most Claude Analytics users.
- File an issue first to discuss the change you wish to make.
- Fork the repo and create your branch from
main. - If you've added code that should be tested, add tests.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
-
Clone the repo:
git clone https://github.com/igeunpyo/claude-analytics.git cd claude-analytics -
Install dependencies:
npm install
-
Run in development mode:
npm run dev
By contributing, you agree that your contributions will be licensed under its MIT License.