docs: Fix npm package name, repository links, and documentation

Author: DVC2

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,45 @@
+---
+name: Bug report
+about: Create a report to help us improve TaskTracker
+title: '[BUG] '
+labels: bug
+assignees: ''
+
+---
+
+## **Bug Description**
+A clear and concise description of what the bug is.
+
+## **To Reproduce**
+Steps to reproduce the behavior:
+1. Run command `tt ...`
+2. With arguments `...`
+3. See error
+
+## **Expected Behavior**
+A clear description of what you expected to happen.
+
+## **Actual Behavior**
+What actually happened instead.
+
+## **Error Output**
+```
+Paste any error messages here
+```
+
+## **Environment**
+- OS: [e.g. macOS 13.0, Ubuntu 20.04, Windows 11]
+- Node.js version: [e.g. 18.17.0]
+- TaskTracker version: [e.g. 3.0.0]
+- Shell: [e.g. bash, zsh, fish]
+
+## **Journal Context** (if relevant)
+- Number of journal entries: [e.g. ~50]
+- Git integration enabled: [yes/no]
+- Project type: [e.g. Node.js, Python, etc.]
+
+## **Additional Context**
+Add any other context about the problem here.
+
+## **Possible Solution** (optional)
+If you have ideas on how to fix this, please share. 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,40 @@
+---
+name: Feature request
+about: Suggest an idea for TaskTracker
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+
+---
+
+## **Is your feature request related to a problem?**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+## **Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+## **Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+## **Use Case**
+Describe how this feature would be used in your workflow:
+- What commands would you run?
+- How often would you use this?
+- What problem does it solve?
+
+## **Example Usage**
+If possible, show what the command/feature would look like:
+```bash
+tt your-new-feature --example
+```
+
+## **Would this be breaking?**
+- [ ] This would break existing functionality
+- [ ] This is purely additive
+- [ ] Not sure
+
+## **Additional context**
+Add any other context, mockups, or screenshots about the feature request here.
+
+## **Implementation Ideas** (optional)
+If you have ideas on how this could be implemented, please share. 

CODE_OF_CONDUCT.md

@@ -0,0 +1,64 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD]. All complaints will be reviewed and investigated
+promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+[homepage]: https://www.contributor-covenant.org 

CONTRIBUTING.md

@@ -1,6 +1,56 @@
 # Contributing to TaskTracker
 
-Thank you for your interest in contributing to TaskTracker! This document provides guidelines and information for contributors.
+We love your input! We want to make contributing to TaskTracker as easy and transparent as possible, whether it's:
+
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+- Becoming a maintainer
+
+## We Develop with GitHub
+
+We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
+
+## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html)
+
+Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `main`.
+2. If you've added code that should be tested, add tests.
+3. If you've changed APIs, update the documentation.
+4. Ensure the test suite passes.
+5. Make sure your code lints.
+6. Issue that pull request!
+
+## Any contributions you make will be under the MIT Software License
+
+In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
+
+## Report bugs using GitHub's [issue tracker](https://github.com/DVC2/task_tracker/issues)
+
+We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/DVC2/task_tracker/issues/new); it's that easy!
+
+## Write bug reports with detail, background, and sample code
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can.
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+
+## Use a Consistent Coding Style
+
+* Use 2 spaces for indentation rather than tabs
+* You can try running `npm run lint` for style unification
+
+## License
+
+By contributing, you agree that your contributions will be licensed under its MIT License.
 
 ## 🚀 Quick Start
 

README.md

@@ -1,6 +1,7 @@
 # TaskTracker: Developer Context Journal 📝
 
-[![npm version](https://badge.fury.io/js/@dvc2%2Ftasktracker-cli.svg)](https://badge.fury.io/js/@dvc2%2Ftasktracker-cli)
+[![npm version](https://badge.fury.io/js/@dvc2%2Ftasktracker-cli.svg)](https://www.npmjs.com/package/@dvc2/tasktracker-cli)
+[![npm downloads](https://img.shields.io/npm/dm/@dvc2/tasktracker-cli.svg)](https://www.npmjs.com/package/@dvc2/tasktracker-cli)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![Node.js CI](https://github.com/DVC2/task_tracker/actions/workflows/test.yml/badge.svg)](https://github.com/DVC2/task_tracker/actions/workflows/test.yml)
 
@@ -41,15 +42,37 @@ tt c  # Quick context
 tt cf # Full context with history
 ```
 
+## 🚀 **Git Integration (NEW!)**
+
+Seamlessly capture your development history:
+```bash
+# Install git hooks for auto-journaling
+tt git-install-hook
+
+# Now every commit automatically creates a journal entry!
+git commit -m "feat: Add user authentication"
+# → Automatically journaled with tags: git, feat, main
+
+# Import recent commits
+tt git-sync 10
+
+# Toggle auto-prompting
+tt git-auto off  # Disable context prompting
+```
+
 ## 📖 **Core Features**
 
 ### Development Journal
 Track your progress, decisions, and blockers:
 ```bash
-tt j "Completed user authentication flow"
-tt j --type decision "Switching from MongoDB to PostgreSQL"
-tt j --type blocker "CORS issues with frontend"
-tt j --tags api,auth "Added rate limiting to login endpoint"
+# Quick aliases for common entries
+tt done "Completed user authentication flow"
+tt decided "Switching from MongoDB to PostgreSQL"
+tt blocked "CORS issues with frontend"
+tt til "Redis connection pooling improves performance"
+
+# Or use the full command
+tt j "Added rate limiting to login endpoint" --tags api,auth
 ```
 
 ### PRD Management
@@ -89,19 +112,19 @@ tt c
 ### During Development
 ```bash
 # Track progress
-tt j "Added user profile endpoints"
+tt done "Added user profile endpoints"
 
 # Document decisions
-tt j --type decision "Using Redis for session storage - built-in expiration"
+tt decided "Using Redis for session storage - built-in expiration"
 
 # Note blockers
-tt j --type blocker "WebSocket connection drops after 30 seconds"
+tt blocked "WebSocket connection drops after 30 seconds"
 ```
 
 ### Debugging with AI
 ```bash
 # Document the issue
-tt j --type blocker "Users can't login - 401 errors"
+tt blocked "Users can't login - 401 errors"
 
 # Add context
 tt j "Checked: JWT secret is correct, token format is valid"
@@ -119,6 +142,18 @@ tt cf 1  # Just today's context
 - `tt journal-search "query"` - Search entries
 - `tt journal-export [format]` - Export journal
 
+### Productivity Aliases
+- `tt done "text"` - Quick progress entry
+- `tt decided "text"` - Quick decision entry
+- `tt blocked "text"` - Quick blocker entry
+- `tt til "text"` - Quick learning entry
+
+### Git Integration
+- `tt git-install-hook` - Install auto-journaling hook
+- `tt git-sync [count]` - Import recent commits
+- `tt git-auto [on|off]` - Toggle auto-prompting
+- `tt git-status` - Show integration status
+
 ### Context Commands  
 - `tt context-quick` (alias: `tt c`) - Quick context
 - `tt context-full [days]` (alias: `tt cf`) - Full context
@@ -157,7 +192,7 @@ tt journal-export json --output backup.json
 
 ## 🎨 **What Makes TaskTracker Different**
 
-1. **Not Another Task Manager** - It's a context journal, not a todo list
+1. **Git Integration** - Automatically captures your development history
 2. **AI-First Design** - Built specifically for AI-assisted development
 3. **Zero Friction** - Simple commands that fit your workflow
 4. **Local & Private** - Your data stays in your project
@@ -185,7 +220,8 @@ See [AI Integration Guide](docs/AI_INTEGRATION_GUIDE.md) for detailed patterns a
 - ✅ All journal functionality (add, show, search, export)
 - ✅ PRD parsing and management
 - ✅ AI context generation (quick & full)
-- ✅ Proper CLI argument parsing
+- ✅ Git integration with auto-journaling
+- ✅ Productivity aliases for quick entries
 - ✅ Clean, maintainable codebase
 - ✅ Comprehensive test coverage
 
@@ -205,45 +241,25 @@ TaskTracker stores all data locally in the `.tasktracker/` directory. This direc
 - Never commit real journal data to public repositories
 - Use the sanitized examples in `examples/` for demos or documentation
 
-If you need to share examples, use the sanitized data in the `examples/` directory instead of your real journal entries.
+## 📚 **Examples & Documentation**
 
-## 🛠️ **Development**
-
-```bash
-# Clone and install
-git clone https://github.com/tasktracker-cli/tasktracker.git
-cd tasktracker
-npm install
-
-# Run tests
-npm test
-
-# Lint code
-npm run lint:check
-npm run lint:fix
-```
-
-See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed development guidelines.
+Check out the [examples directory](examples/) for:
+- Sample journal entries
+- Example configurations
+- Usage patterns
+- Best practices
 
 ## 🤝 **Contributing**
 
-We welcome contributions! Please see our [Contributing Guide](CONTRIBUTING.md) for details.
-
-### Quick Contribution Steps
-1. Fork the repository
-2. Create a feature branch
-3. Make your changes with tests
-4. Submit a pull request
-
-## 🐛 **Issues & Support**
-
-- **Bug Reports**: [GitHub Issues](https://github.com/tasktracker-cli/tasktracker/issues)
-- **Feature Requests**: [GitHub Discussions](https://github.com/tasktracker-cli/tasktracker/discussions)
-- **Documentation**: [docs/](docs/) directory
+We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for:
+- Development setup
+- Code style guide
+- Pull request process
+- Testing requirements
 
 ## 📄 **License**
 
-MIT License - see [LICENSE](LICENSE) file for details.
+TaskTracker is [MIT licensed](LICENSE).
 
 ## 🙏 **Acknowledgments**