devdaily-ai 0.5.0 → 0.6.1

package/CHANGELOG.md

@@ -0,0 +1,203 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.6.1] - 2026-02-15
+
+### Fixed
+
+- **Slack webhook formatting** — Standup messages sent to Slack via `--send` / `--slack` now correctly render bold, italic, and other formatting. Previously, raw Markdown syntax (e.g. `**bold**`) was sent directly into Slack's `mrkdwn` blocks, which don't support double-asterisk bold. The notification pipeline now converts Markdown → Slack mrkdwn format using the existing `formatOutput()` formatter before sending, so `**text**` becomes `*text*`, `*italic*` becomes `_italic_`, headers become bold lines, and links use Slack's `<url|text>` syntax.
+
+## [0.5.0] - 2025-07-13
+
+### Added
+
+- **Persistent Work Journal** — Local work memory stored in `~/.config/devdaily/journal/` that tracks your work across sessions, days, and projects.
+  - `src/core/work-journal.ts` — Full storage layer with index, search, merge, cross-project aggregation, pruning, and stats.
+  - `src/core/snapshot-builder.ts` — Captures rich repo state (branches, commits, PRs, tickets, diffs, categories) into `WorkSnapshot` objects.
+
+- **`devdaily snapshot`** (`snap`, `save`) — Manually capture a work snapshot with notes and tags.
+  - `--light` mode for fast captures (no PRs/tickets).
+  - `--list [days]` to browse recent snapshots.
+  - `--stats` to see journal storage usage.
+  - `--prune <days>` to clean up old entries.
+
+- **`devdaily context`** (`ctx`, `resume`) — Recover what you were working on after a context switch.
+  - Date range filtering (`--from`, `--to`, `--date`, `--days`).
+  - `--all-projects` for cross-project context.
+  - `--ai` for AI-powered "where did I leave off?" summaries.
+  - `--branches` for detailed active branch status.
+
+- **`devdaily recall`** (`search`, `find`) — Search your work history by keyword, file, tag, or date range.
+  - Fuzzy matching across commit messages, branch names, notes, and tags.
+  - `--file <path>` to find when a specific file was changed.
+  - `--ai` for AI-powered search result summaries.
+  - `--json` output for scripting.
+
+- **Automatic Side-Effect Snapshots** — Zero-friction snapshot capture.
+  - `src/core/auto-snapshot.ts` — Silent, non-blocking snapshot module.
+  - `sideEffectSnapshot()` runs at the end of `standup`, `pr`, and `week` commands.
+  - `fireAndForgetSnapshot()` for fully async background captures.
+  - Tagged with source (`auto:standup`, `auto:pr`, `auto:week`, etc.).
+  - Respects `journal.autoSnapshot` config flag.
+  - `--no-journal` flag on `standup` and `pr`, `--no-auto-snapshot` on `week` to skip.
+
+- **Git Hooks for Auto-Capture** — Opt-in `post-commit` and `post-checkout` hooks.
+  - `devdaily init --git-hooks` — Interactive hook installer.
+  - `devdaily init --remove-hooks` — Clean removal of devdaily hooks.
+  - POSIX-compatible (`#!/bin/sh`), background-executed, safe with existing hooks.
+  - Appends to existing hooks rather than overwriting.
+  - `generatePostCommitHook()` and `generatePostCheckoutHook()` in `auto-snapshot.ts`.
+
+- **`journal` Config Section** — New configuration block for snapshot automation.
+  - `autoSnapshot` (default: `true`) — Enable/disable side-effect snapshots globally.
+  - `gitHooks` (default: `false`) — Track whether git hooks are installed.
+  - `hooks.postCommit` / `hooks.postCheckout` — Per-hook enable/disable.
+  - `quiet` (default: `true`) — Suppress snapshot side-effect messages.
+
+- **Enhanced `devdaily week`** — Major improvements to weekly summaries.
+  - `--from` / `--to` for custom date ranges.
+  - `--weeks-ago <n>` for relative week selection.
+  - `--all-projects` for cross-project summaries from journal data.
+  - `--save` to persist the AI summary to the journal.
+  - `--json` for machine-readable stats output.
+  - Journal enrichment — weekly summaries incorporate snapshot history.
+
+- **Comprehensive Test Suite** — 654 tests across 12 test files.
+  - `tests/auto-snapshot.test.ts` — 74 tests covering side-effect snapshots, hook generation, hook install/remove, config integration, edge cases, and round-trip cycles.
+  - `tests/work-journal.test.ts` — 123 tests covering persistent storage, search, cross-project aggregation, merge logic, pruning, and stats.
+
+- **Production-Grade README** — Complete rewrite with full command reference, config documentation, architecture overview, testing guide, FAQ, and troubleshooting.
+
+### Changed
+
+- **`devdaily init`** — Added `📸 Git hooks for automatic snapshots` as an interactive setup option, `--git-hooks` and `--remove-hooks` flags, and `dd context` in quick-start hints.
+- **`devdaily standup`** — Now auto-saves a light snapshot to the journal after generating (disable with `--no-journal`).
+- **`devdaily pr`** — Now auto-saves a light snapshot to the journal after generating (disable with `--no-journal`).
+- **`devdaily week`** — Now auto-saves a light snapshot to the journal after generating (disable with `--no-auto-snapshot`).
+- **Config schema** — Added `JournalSchema` with `autoSnapshot`, `gitHooks`, `hooks`, `autoPromptDays`, and `quiet` fields. Exported `Journal` type.
+- **README** — Rewritten from scratch to production-grade standard. Updated project structure, feature table, command reference, config examples, roadmap (marked completed items), and added sections for auto-snapshots, privacy, and testing.
+
+### Technical
+
+- New modules: `src/core/auto-snapshot.ts`, `src/core/snapshot-builder.ts`, `src/core/work-journal.ts`.
+- New commands: `src/commands/snapshot.ts`, `src/commands/context.ts`, `src/commands/recall.ts`.
+- New test file: `tests/auto-snapshot.test.ts` (74 tests).
+- Total test count: 580 → 654 (12 test files).
+- Build output: 348 KB (ESM), clean TypeScript compilation with zero errors.
+
+## [0.4.1] - 2026-02-14
+
+### Fixed
+
+- **Jira ADF Description Crash** — `ticket.description.trim is not a function` when using Jira Cloud API v3. Jira returns `description` as an Atlassian Document Format (ADF) object, not a plain string. Added `extractAdfText()` recursive parser to convert ADF trees to plain text.
+- **Defensive Description Handling** — Added `typeof` guards before calling string methods on `ticket.description` in `formatForPrompt()`, `formatTicketForContext()`, and `formatTicketContext()` to prevent crashes from any non-string description values.
+- **Silent PM Fetch Failures** — `fetchTickets()` had a bare `catch {}` that returned `[]` on any error, making PM integration failures invisible. Now logs diagnostic info when `--debug` flag is active.
+
+### Added
+
+- **PM Integration Test Suite** — End-to-end test scripts for GitHub Issues and Linear integrations:
+  - `scripts/setup-test-repo.sh` — Creates a disposable GitHub repo with issues, source files, and initial commit
+  - `scripts/setup-test-commits.sh` — Creates branches, commits, and PRs referencing both GitHub and Linear ticket IDs
+  - `scripts/create-linear-issues.py` — Creates matching Linear issues via GraphQL API
+- **PM Integration Test Report** — Comprehensive test report at `docs/reports/PM_INTEGRATION_TEST_REPORT.md` documenting test matrix, results, bugs found, and fixes applied across GitHub Issues, Linear, and Jira
+- **Debug Logging for Ticket Fetching** — `--debug` flag now surfaces `[fetchTickets]` messages showing PM client configuration status, fetch progress, and errors
+- **`debug` option in `StandupContextOptions`** — Passed through from both `standup` and `week` commands to enable ticket fetch diagnostics
+
+### Changed
+
+- Updated `docs/TESTING.md` with PM integration testing section, setup instructions, verification checklist, and troubleshooting guide
+
+## [0.3.0] - 2026-02-14
+
+### Added
+
+- **Context Analyzer** - Smart work context extraction from git activity
+  - Branch → Ticket correlation (JIRA-123, #123, LINEAR-123 patterns)
+  - Work categorization (frontend, backend, infra, docs, tests, config)
+  - Time-based work session tracking
+- **Enhanced Standup Context** - `--context` flag shows detailed work analysis
+- **JSON Schema for IDE** - Autocomplete support in `.devdaily.json` config files
+- **PR Config Defaults** - Set default reviewers, assignees, and labels in config
+- **Standup Scheduling** - Configure standup schedule and grouping options
+
+### Changed
+
+- Config now includes `$schema` reference for IDE autocomplete
+- Standup generation uses work categories and ticket context for better AI summaries
+- Expanded PR and standup config options (defaultReviewers, defaultLabels, groupBy, etc.)
+
+### Technical
+
+- New `src/core/context-analyzer.ts` for rich context extraction
+- Added `schemas/devdaily.schema.json` for config validation
+- Updated config schema with more standup/PR options
+
+## [0.2.0] - 2026-02-13
+
+### Added
+
+- **PR Template Support** - Auto-detect and parse `.github/PULL_REQUEST_TEMPLATE.md`
+- **AI Template Filling** - Copilot fills template sections based on commit analysis
+- **PR Preview** - Terminal markdown rendering with `--preview` flag
+- **Interactive PR Mode** - Select labels, reviewers, assignees with `--interactive`
+- **Slack Notifications** - Send standups to Slack via webhooks with `--slack`
+- **Discord Notifications** - Send standups to Discord via webhooks with `--discord`
+- **Config Management** - New `devdaily config` command for managing settings
+- **Init Wizard** - Interactive setup with `devdaily init` command
+- **Notifications Setup** - `devdaily init --notifications` for webhook configuration
+- **Doctor Command** - `devdaily doctor` to diagnose and fix setup issues
+- **Dashboard Command** - `devdaily dash` for quick status overview (stub)
+- **Project Management Integration** - Jira, Linear, Notion support (stub)
+- **Secrets Management** - Secure storage for API keys and webhooks
+- **Custom UI System** - Enhanced terminal UI with colors, ASCII art, and help rendering
+
+### Changed
+
+- Upgraded to new GitHub Copilot CLI (`copilot -p --silent`)
+- Improved PR description generation with template awareness
+- Better error handling and user feedback
+- Enhanced standup formatting for notification channels
+
+### Fixed
+
+- TypeScript strict mode compliance
+- Unused variable warnings in doctor and github modules
+
+## [0.1.0] - 2026-02-12
+
+### Added
+
+- Initial release of DevDaily AI
+- `standup` command - Generate daily standup notes from git commits
+- `pr` command - Generate PR descriptions with interactive preview
+- `week` command - Generate weekly work summaries
+- `context` command - Recover work context (stub)
+- Commitlint integration for smart PR title generation
+- Interactive PR workflow (preview, create, draft)
+- Auto-copy to clipboard for all outputs
+- Multiple output formats (markdown, slack, plain)
+- Professional terminal UI (chalk, boxen, ora)
+- Comprehensive test suite (9 tests)
+- GitHub Actions CI/CD
+- Husky pre-commit hooks
+- ESLint + Prettier formatting
+- TypeScript strict mode
+
+### Features
+
+- GitHub Copilot CLI integration for AI-powered summaries
+- Conventional commit parsing
+- Issue number extraction from commits
+- PR type categorization (feature, bugfix, breaking)
+- Support for custom date ranges
+- No emoji output (professional terminal style)
+
+[0.5.0]: https://github.com/hempun10/devdaily/releases/tag/v0.5.0
+[0.4.1]: https://github.com/hempun10/devdaily/releases/tag/v0.4.1
+[0.3.0]: https://github.com/hempun10/devdaily/releases/tag/v0.3.0
+[0.2.0]: https://github.com/hempun10/devdaily/releases/tag/v0.2.0
+[0.1.0]: https://github.com/hempun10/devdaily/releases/tag/v0.1.0

package/CONTRIBUTING.md

@@ -0,0 +1,264 @@
+# Contributing to DevDaily
+
+Thank you for your interest in contributing to DevDaily! This guide will help you get started.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Getting Started](#getting-started)
+- [Development Workflow](#development-workflow)
+- [Coding Standards](#coding-standards)
+- [Commit Convention](#commit-convention)
+- [Pull Request Process](#pull-request-process)
+- [Testing](#testing)
+- [Project Structure](#project-structure)
+- [Reporting Issues](#reporting-issues)
+
+## Code of Conduct
+
+This project follows the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior by opening an issue.
+
+## Getting Started
+
+### Prerequisites
+
+- [Node.js](https://nodejs.org) >= 18.0.0
+- [Git](https://git-scm.com)
+- [GitHub CLI](https://cli.github.com) (`gh`) — for testing PR creation features
+- [GitHub Copilot CLI](https://github.com/github/gh-copilot) — for testing AI generation features
+
+### Setup
+
+```bash
+# Fork the repository on GitHub, then:
+git clone https://github.com/<your-username>/devdaily.git
+cd devdaily
+npm install
+
+# Verify everything works
+npm run typecheck
+npm run lint
+npm test
+npm run build
+```
+
+### Running locally
+
+```bash
+# Watch mode — rebuilds on file changes
+npm run dev
+
+# Link the CLI globally for manual testing
+npm link
+
+# Now you can test commands in any git repo
+devdaily standup --days 1 --no-copy
+devdaily pr --debug
+```
+
+## Development Workflow
+
+1. **Create a branch** from `main`:
+
+   ```bash
+   git checkout -b feat/your-feature-name
+   ```
+
+2. **Make your changes** — write code, add tests, update docs.
+
+3. **Run the quality checks:**
+
+   ```bash
+   npm run typecheck   # TypeScript compilation
+   npm run lint        # ESLint
+   npm run format      # Prettier formatting
+   npm test            # Vitest test suite
+   npm run build       # Production build
+   ```
+
+4. **Commit your changes** following the [commit convention](#commit-convention).
+
+5. **Push and open a pull request** against `main`.
+
+## Coding Standards
+
+### TypeScript
+
+- **Strict mode** is enabled — no `any` types unless absolutely necessary (use `unknown` and narrow).
+- All new functions should have JSDoc comments describing their purpose.
+- Prefer `async/await` over raw promises.
+- Use `readonly` for properties and parameters that should not be mutated.
+
+### Style
+
+These are enforced by ESLint and Prettier (run automatically on commit via Husky):
+
+- 2-space indentation
+- Single quotes
+- Semicolons required
+- Trailing commas (`es5` style)
+- 100-character line width
+- LF line endings
+
+```bash
+# Auto-fix formatting
+npm run lint:fix
+npm run format
+```
+
+### File organization
+
+- **One export per file** when possible — makes imports clear.
+- **Co-locate tests** in the `tests/` directory, matching the source file name (e.g., `src/core/notifications.ts` → `tests/notifications.test.ts`).
+- **Keep commands thin** — commands in `src/commands/` should orchestrate, not contain business logic. Business logic goes in `src/core/`.
+
+## Commit Convention
+
+We use [Conventional Commits](https://www.conventionalcommits.org/). This is enforced by commitlint on every commit.
+
+### Format
+
+```
+<type>(<optional scope>): <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+### Types
+
+| Type       | Description                                             |
+| ---------- | ------------------------------------------------------- |
+| `feat`     | A new feature                                           |
+| `fix`      | A bug fix                                               |
+| `docs`     | Documentation only changes                              |
+| `style`    | Formatting, missing semicolons, etc. (no logic)         |
+| `refactor` | Code change that neither fixes a bug nor adds a feature |
+| `perf`     | Performance improvement                                 |
+| `test`     | Adding or updating tests                                |
+| `build`    | Changes to build system or dependencies                 |
+| `ci`       | Changes to CI configuration                             |
+| `chore`    | Other changes that don't modify src or tests            |
+| `revert`   | Reverts a previous commit                               |
+
+### Examples
+
+```bash
+feat: add JSON output format for standup command
+fix(pr): handle repos with no default branch configured
+docs: update installation instructions for Linux
+test: add webhook notification integration tests
+refactor(journal): extract snapshot serialization logic
+```
+
+### Rules
+
+- Use lowercase for the description (no `Fix Bug` — use `fix bug`).
+- Do not end the subject line with a period.
+- Use the imperative mood ("add feature" not "added feature").
+
+## Pull Request Process
+
+1. **Fill out the PR template** — describe what changed and why.
+2. **Keep PRs focused** — one feature or fix per PR. Large PRs are harder to review.
+3. **Add tests** for new features and bug fixes.
+4. **Update documentation** if your change affects user-facing behavior (README, help text, etc.).
+5. **Make sure CI passes** — the PR must pass typecheck, lint, format check, tests, and build.
+6. **Respond to review feedback** — we aim to review PRs within a few days.
+
+### PR title format
+
+Use the same [conventional commit format](#format) for PR titles:
+
+```
+feat: add Slack thread support for notifications
+fix: clipboard copy failing on plain format
+```
+
+## Testing
+
+We use [Vitest](https://vitest.dev/) for testing.
+
+```bash
+npm test                                    # Run all tests
+npx vitest run tests/notifications.test.ts  # Run a specific file
+npm run test:watch                          # Watch mode
+npm run test:coverage                       # With coverage report
+```
+
+### Writing tests
+
+- Place test files in `tests/` with a `.test.ts` suffix.
+- Mock external dependencies (git, Copilot CLI, APIs) — tests should not require network access.
+- Use `describe`/`it` blocks with clear, descriptive names.
+- Test both the happy path and error/edge cases.
+
+### Test structure example
+
+```typescript
+import { describe, it, expect, vi } from 'vitest';
+
+describe('formatOutput', () => {
+  describe('plain format', () => {
+    it('strips markdown headers', () => {
+      // arrange
+      const input = '## Completed\n\n- Task A';
+      // act
+      const result = formatOutput(input, 'plain');
+      // assert
+      expect(result.text).not.toContain('##');
+      expect(result.text).toContain('Completed:');
+    });
+  });
+});
+```
+
+## Project Structure
+
+```
+src/
+├── commands/       # CLI command handlers (thin orchestration layer)
+├── core/           # Business logic (git analysis, AI, journal, notifications)
+├── config/         # Configuration loading, schema (Zod), secrets management
+├── ui/             # Terminal UI rendering (colors, ASCII art, help screens)
+├── utils/          # Shared utilities (clipboard, date helpers, formatting)
+├── types/          # TypeScript type definitions
+└── index.ts        # CLI entry point (Commander.js setup)
+
+tests/              # Vitest test suites (mirrors src/ structure)
+schemas/            # JSON Schema for .devdaily.json IDE autocomplete
+examples/           # Example command outputs for documentation
+```
+
+## Reporting Issues
+
+### Bug reports
+
+When filing a bug report, please include:
+
+1. **DevDaily version** (`devdaily --version`)
+2. **Node.js version** (`node --version`)
+3. **Operating system**
+4. **Steps to reproduce** — what commands you ran
+5. **Expected vs. actual behavior**
+6. **Debug output** — run the failing command with `--debug` and include the output
+
+### Feature requests
+
+We welcome feature ideas! Please:
+
+- Check existing issues to avoid duplicates.
+- Describe the problem your feature would solve.
+- Suggest a possible approach if you have one.
+- Label with `enhancement`.
+
+---
+
+## Need Help?
+
+- Browse [existing issues](https://github.com/hempun10/devdaily/issues)
+- Read the [README](README.md) for usage documentation
+- Run `devdaily doctor` to diagnose setup problems
+
+Thank you for contributing!

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 DevDaily AI
+Copyright (c) 2025 Hem Pun
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal