pet-terminal 1.0.0 → 1.0.2

package/.eslintrc.json

@@ -0,0 +1,22 @@
+{
+  "parser": "@typescript-eslint/parser",
+  "extends": [
+    "eslint:recommended",
+    "plugin:@typescript-eslint/recommended"
+  ],
+  "plugins": ["@typescript-eslint"],
+  "parserOptions": {
+    "ecmaVersion": 2020,
+    "sourceType": "module",
+    "project": "./tsconfig.json"
+  },
+  "rules": {
+    "@typescript-eslint/no-explicit-any": "warn",
+    "@typescript-eslint/explicit-function-return-type": "off",
+    "@typescript-eslint/no-unused-vars": ["error", { "argsIgnorePattern": "^_" }]
+  },
+  "env": {
+    "node": true
+  },
+  "ignorePatterns": ["**/__tests__/**", "**/*.test.ts", "dist", "node_modules"]
+}

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,54 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Describe the Bug
+
+A clear and concise description of what the bug is.
+
+## To Reproduce
+
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Run '....'
+3. Scroll down to '....'
+4. See error
+
+## Expected Behavior
+
+A clear and concise description of what you expected to happen.
+
+## Screenshots
+
+If applicable, add screenshots to help explain your problem.
+
+## Environment
+
+| Setting | Value |
+|---------|-------|
+| OS | [e.g. Windows 11, macOS 14, Ubuntu 22.04] |
+| Node Version | [e.g. v20.10.0] |
+| Pet Terminal Version | [e.g. 1.0.0] |
+
+**Check version with:** `pet --version`
+
+## Additional Context
+
+Add any other context about the problem here.
+
+- Pet species: [e.g. Cat, Dog, etc.]
+- Pet level: [e.g. Level 5]
+- Time since last sync: [e.g. 2 days]
+
+## Console Output
+
+If applicable, paste the console output below:
+
+```
+[paste output here]
+```

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,35 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Feature Description
+
+A clear and concise description of the feature you'd like to see added to Pet Terminal.
+
+## Problem Statement
+
+What problem does this feature solve? Is your feature request related to a problem?
+
+## Proposed Solution
+
+A clear and concise description of what you want to happen.
+
+## Alternative Solutions
+
+Describe any alternative solutions or features you've considered.
+
+## Examples
+
+If applicable, add examples to help illustrate your feature:
+
+```
+pet [new-command] --option
+```
+
+## Additional Context
+
+Add any other context, mockups, or screenshots about the feature request here.

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,69 @@
+## Description
+
+A clear and concise description of what this PR changes.
+
+## Type of Change
+
+Mark the relevant type with an `x`:
+
+- [ ] `feat` - New feature
+- [ ] `fix` - Bug fix
+- [ ] `docs` - Documentation changes
+- [ ] `refactor` - Code refactoring (no functional changes)
+- [ ] `perf` - Performance improvements
+- [ ] `style` - Code style changes (formatting, etc.)
+- [ ] `test` - Adding or updating tests
+- [ ] `chore` - Maintenance tasks
+
+## Related Issue
+
+Fixes #(issue number)
+Related to #(issue number)
+
+## Changes Made
+
+Briefly describe the main changes:
+
+-
+
+-
+
+-
+
+## Testing
+
+Describe the testing you performed:
+
+- [ ] Tested locally with `npm run build && npm link`
+- [ ] All linting passes (`npm run lint`)
+- [ ] Manual testing steps performed:
+
+```
+[describe steps to test]
+```
+
+## Screenshots (if applicable)
+
+Add screenshots to help verify your changes.
+
+## Breaking Changes
+
+Does this PR introduce any breaking changes?
+
+- [ ] Yes (describe below)
+- [ ] No
+
+If yes, please describe:
+
+## Checklist
+
+- [ ] My code follows the project's style guidelines
+- [ ] I have performed a self-review of my code
+- [ ] I have commented my code where necessary
+- [ ] I have updated the documentation accordingly
+- [ ] My changes generate no new warnings
+- [ ] I have tested my changes locally
+
+## Additional Notes
+
+Any additional notes for the reviewer.

package/.github/workflows/ci.yml

@@ -0,0 +1,62 @@
+name: CI
+
+on:
+  push:
+    branches: [master, main]
+  pull_request:
+    branches: [master, main]
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+        node-version: [18.x, 20.x]
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run linter
+        run: npm run lint
+
+      - name: Build project
+        run: npm run build
+
+      - name: Run tests
+        run: npm test
+
+  coverage:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20.x
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run coverage
+        run: npm run test:coverage
+
+      - name: Upload coverage to Codecov
+        uses: codecov/codecov-action@v4
+        with:
+          files: ./coverage/coverage-final.json
+          flags: unittests
+          name: codecov-umbrella
+        continue-on-error: true

package/.prettierrc

@@ -0,0 +1,8 @@
+{
+  "semi": true,
+  "trailingComma": "es5",
+  "singleQuote": true,
+  "printWidth": 80,
+  "tabWidth": 2,
+  "useTabs": false
+}

package/.vscodeignore

@@ -0,0 +1,17 @@
+# VS Code ignore file - excludes files from extension package
+.vscode/**
+.github/**
+src/**
+**/*.map
+**/*.ts
+tsconfig.json
+vitest.config.ts
+.eslintrc.json
+.prettierrc
+.gitignore
+*.log
+node_modules/**
+CHANGELOG.md
+CONTRIBUTING.md
+CODE_OF_CONDUCT.md
+# Keep dist (compiled JS), README, LICENSE, and package.json

package/CHANGELOG.md

@@ -0,0 +1,63 @@
+# Changelog
+
+All notable changes to Pet Terminal will be documented in this file.
+
+## [1.0.2] - 2025-12-31
+
+### Added - VS Code Extension
+- Full VS Code Extension support with Status Bar integration
+- Webview Dashboard with Tamagotchi-style visual interface and retro ASCII art
+- Native Git monitoring via VS Code API - earn XP by committing code
+- Interactive Commands via Command Palette (Feed, Play, Release)
+- Real-time status updates every 3 seconds
+
+### Added - New Features
+- `pet release` command - say goodbye to your pet forever (CLI and VS Code)
+- Modal confirmation dialogs for pet release in VS Code
+
+### Changed
+- Simplified species from 6 to 2 (Cat and Dog) for improved ASCII art quality
+- Each species now has distinct, recognizable ASCII art:
+  - Cat: Pointed ears `/\_/\`, whiskers `># #<`
+  - Dog: Floppy ears `__ /__`, rounder face
+- Updated README to reflect hybrid CLI + VS Code nature
+- Updated installation instructions with VS Code `.vsix` support
+
+### Removed
+- Rabbit, Hamster, Bird, and Dragon species (art quality improvement)
+- dragon_gem item (no longer applicable)
+
+## [1.0.1] - 2025-12-30
+
+### Fixed
+- Database path: Changed from `process.cwd()/data/pet.json` to `~/.pet-terminal/pet.json`
+- Git availability check logic bug
+- Version display now reads from package.json
+- XP progress bar display format
+- Database path consistency in welcome screen
+- Configuration comments to match actual decay rates
+
+### Added
+- Unit tests for core functionality (72 tests)
+- CI/CD pipeline with GitHub Actions
+
+## [1.0.0] - 2025-12-30
+
+### Added
+- Virtual pet system with 6 species: Cat, Dog, Rabbit, Hamster, Bird, Dragon
+- Pet stats: Hunger, Happiness, Health, Cleanliness, Energy
+- Level system with XP progression
+- Mood states: Happy, Neutral, Sad, Critical, Sleeping
+- Git commit detection with coin and XP rewards
+- Shop system with food, toys, medicine, and cleaning supplies
+- Inventory management
+- One-click care command (`pet care`)
+- Interactive tutorial for new users
+- Colorful terminal output with ASCII art
+- Config file support at `~/.pet-terminal/config.json`
+
+---
+
+[1.0.2]: https://github.com/lessen-xu/pet-terminal/releases/tag/v1.0.2
+[1.0.1]: https://github.com/lessen-xu/pet-terminal/releases/tag/v1.0.1
+[1.0.0]: https://github.com/lessen-xu/pet-terminal/releases/tag/v1.0.0

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# 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, caste, color, 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
+
+Project maintainers are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project maintainers at lessenx2002@gmail.com. All complaints
+will be reviewed and investigated promptly and fairly.
+
+All project maintainers are obligated to respect the privacy and security of
+the reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][version].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[version]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -0,0 +1,193 @@
+# Contributing to Pet Terminal
+
+First off, thank you for considering contributing to Pet Terminal! It's people like you that make Pet Terminal such a great tool.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [How Can I Contribute?](#how-can-i-contribute)
+- [Development Setup](#development-setup)
+- [Coding Guidelines](#coding-guidelines)
+- [Commit Message Conventions](#commit-message-conventions)
+- [Submitting Changes](#submitting-changes)
+
+## Code of Conduct
+
+By participating in this project, you agree to maintain a respectful and inclusive environment. Please see [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) for details.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+Before creating bug reports, please check the existing issues to avoid duplicates. When you create a bug report, include as many details as possible using the [Bug Report template](.github/ISSUE_TEMPLATE/bug_report.md).
+
+### Suggesting Enhancements
+
+Enhancement suggestions are tracked as GitHub issues. When creating an enhancement suggestion, include:
+- A clear title and description
+- Specific use cases
+- Possible implementation ideas (if you have them)
+
+### Pull Requests
+
+Pull requests are welcome! Here's how to get started:
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Commit your changes (follow [commit message conventions](#commit-message-conventions))
+5. Push to the branch (`git push origin feature/amazing-feature`)
+6. Open a Pull Request
+
+## Development Setup
+
+### Prerequisites
+
+- Node.js >= 14.0.0
+- npm or yarn
+
+### Installation
+
+```bash
+# Clone your fork
+git clone https://github.com/your-username/pet-terminal.git
+cd pet-terminal
+
+# Install dependencies
+npm install
+
+# Build the project
+npm run build
+
+# Link for local testing
+npm link
+```
+
+### Running Commands
+
+```bash
+# Run in development mode
+npm run dev
+
+# Run linting
+npm run lint
+
+# Build for production
+npm run build
+```
+
+### Project Structure
+
+```
+pet-terminal/
+├── src/
+│   ├── commands/       # CLI commands (init, feed, play, etc.)
+│   ├── core/           # Core logic (pet, inventory, shop, database)
+│   ├── monitor/        # Git monitoring and activity tracking
+│   ├── types/          # TypeScript type definitions
+│   ├── ui/             # Display and UI components
+│   └── index.ts        # Entry point
+├── data/               # Local data storage (gitignored)
+└── dist/               # Compiled JavaScript output
+```
+
+## Coding Guidelines
+
+### TypeScript
+
+- Use TypeScript for all new code
+- Avoid using `any` type when possible
+- Use interfaces for object shapes
+- Add JSDoc comments for exported functions
+
+### Code Style
+
+- Use 2 spaces for indentation
+- Use single quotes for strings
+- Use const by default, let when reassignment is needed
+- Follow existing naming conventions (camelCase for variables, PascalCase for classes)
+
+### Error Handling
+
+```typescript
+// Always handle errors gracefully
+try {
+  // operation
+} catch (error) {
+  console.error(chalk.red('Error:'), error instanceof Error ? error.message : error);
+  process.exit(1);
+}
+```
+
+### User Experience
+
+- Always provide clear feedback to users
+- Use chalk for colored terminal output
+- Include helpful error messages with suggested actions
+- Test edge cases (no pet found, low stats, etc.)
+
+## Commit Message Conventions
+
+We use semantic commit messages to make changelog generation easier:
+
+```
+<type>(<scope>): <description>
+
+[optional body]
+
+[optional footer]
+```
+
+### Types
+
+| Type | Description |
+|------|-------------|
+| `feat` | New feature |
+| `fix` | Bug fix |
+| `docs` | Documentation only changes |
+| `style` | Code style changes (formatting, etc.) |
+| `refactor` | Code refactoring |
+| `perf` | Performance improvements |
+| `test` | Adding or updating tests |
+| `chore` | Maintenance tasks |
+
+### Examples
+
+```
+feat(commands): add new pet grooming command
+
+fix: resolve issue with pet stats not saving correctly
+
+docs: update README with new installation instructions
+
+refactor(core): simplify inventory management logic
+```
+
+## Submitting Changes
+
+### Before Submitting
+
+- [ ] Run `npm run lint` and fix any issues
+- [ ] Run `npm run build` to ensure compilation works
+- [ ] Test your changes manually
+- [ ] Update documentation if needed
+
+### Pull Request Checklist
+
+- [ ] PR title follows semantic commit conventions
+- [ ] PR description clearly describes changes
+- [ ] Code follows project guidelines
+- [ ] No new linting warnings
+- [ ] All changes are tested
+
+## Getting Help
+
+If you need help:
+
+- Open a GitHub issue with the `question` label
+- Check existing documentation in the README
+- Run `pet tutorial` for a guide to using the CLI
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).