Thank you for your interest in contributing to the Claude Code Guide! This document provides guidelines for contributions.
- Use GitHub Issues to report bugs or suggest improvements
- Check existing issues first to avoid duplicates
- Provide clear reproduction steps for bugs
- Include Claude Code version and environment details
- Open a GitHub Issue with the
enhancementlabel - Describe the problem your enhancement solves
- Include evidence or metrics if available
- Reference existing patterns where applicable
- Fork the repository and create your branch from
main - Follow the existing structure - Match the style of existing documentation
- Include evidence - All patterns should have production metrics or test results
- Update the sitemap if adding new pages
- Test locally - Ensure Jekyll builds correctly
- Use kebab-case for file names:
my-new-guide.md - Prefix guide files with numbers for ordering:
36-new-feature.md
# Title
**Created**: YYYY-MM-DD
**Category**: hooks | skills | mcp | optimization
## Problem Statement
What issue does this solve?
## Solution
The approach and implementation.
## Evidence
Metrics, test results, or production data.
## Quick Reference
Key commands or patterns.All optimizations should include measurable results:
- Before/after comparisons
- Time savings
- Token reduction percentages
- Accuracy improvements
- Be respectful and inclusive
- Focus on constructive feedback
- Welcome newcomers and help them get started
- Clone the repository
- Install Jekyll:
gem install jekyll bundler - Run locally:
bundle exec jekyll serve - Make your changes
- Submit a pull request
Open an issue with the question label.
Thank you for helping improve Claude Code Guide!