gitglimpse 0.1.0__tar.gz

gitglimpse-0.1.0/.gitignore

@@ -0,0 +1,215 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/
+*.iml
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# macOS
+.DS_Store
+
+# Build
+*.pyc
+.venv/

gitglimpse-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 dinooo06
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

gitglimpse-0.1.0/PKG-INFO

@@ -0,0 +1,23 @@
+Metadata-Version: 2.4
+Name: gitglimpse
+Version: 0.1.0
+Summary: Analyze git history and generate standup updates, daily reports, and weekly summaries.
+Project-URL: Homepage, https://github.com/dino/gitglimpse
+Project-URL: Repository, https://github.com/dino/gitglimpse
+Project-URL: Bug Tracker, https://github.com/dino/gitglimpse/issues
+Author: Dino
+License: MIT
+License-File: LICENSE
+Keywords: cli,developer-tools,git,standup
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Requires-Dist: inquirerpy>=0.3.4
+Requires-Dist: platformdirs>=4.0
+Requires-Dist: rich>=13.0
+Requires-Dist: tomli-w>=1.2
+Requires-Dist: typer[all]>=0.9.0
+Provides-Extra: llm
+Requires-Dist: httpx>=0.27; extra == 'llm'

gitglimpse-0.1.0/pyproject.toml

@@ -0,0 +1,45 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "gitglimpse"
+version = "0.1.0"
+description = "Analyze git history and generate standup updates, daily reports, and weekly summaries."
+authors = [{ name = "Dino" }]
+license = { text = "MIT" }
+requires-python = ">=3.11"
+keywords = ["git", "standup", "developer-tools", "cli"]
+classifiers = [
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+]
+dependencies = [
+    "typer[all]>=0.9.0",
+    "rich>=13.0",
+    "platformdirs>=4.0",
+    "tomli_w>=1.2",
+    "InquirerPy>=0.3.4",
+]
+
+[project.urls]
+Homepage = "https://github.com/dino/gitglimpse"
+Repository = "https://github.com/dino/gitglimpse"
+"Bug Tracker" = "https://github.com/dino/gitglimpse/issues"
+
+[project.optional-dependencies]
+llm = ["httpx>=0.27"]
+
+[project.scripts]
+glimpse = "gitglimpse.cli:app"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/gitglimpse"]
+
+[tool.hatch.build.targets.wheel.shared-data]
+# Ensures .md templates are included in the wheel alongside Python files.
+
+[tool.hatch.build.targets.sdist]
+include = ["src/gitglimpse/commands/*.md"]

gitglimpse-0.1.0/src/gitglimpse/commands/report.md

@@ -0,0 +1,33 @@
+Generate a detailed daily report from your git commits.
+
+Run the following shell command and capture its output:
+
+```
+glimpse standup --json
+```
+
+Then format the JSON result into a **Markdown daily report** using this structure:
+
+```markdown
+# Daily Report — [date formatted as "Month D, YYYY"]
+
+[For each entry in the "days" array:]
+## [entry "label"] — [entry "date"]
+
+[For each task in the day's "tasks" array:]
+### [branch or "general"] — [commits] commit(s), ~[estimated_minutes/60 rounded]h
+
+**Changes:** +[insertions] −[deletions]
+
+[Plain-English description of what was accomplished, derived from the task summary
+and commit_messages. 2–4 sentences max. Professional but direct.]
+```
+
+Rules:
+- Iterate the "days" array in order. Each day becomes a level-2 section.
+- One level-3 section per task within each day.
+- Derive the description from "summary" and "commit_messages" — do not invent work.
+- If insertions + deletions > 200, note it was a substantial change set.
+- Do NOT add a section with plans or next steps. Only report completed work.
+- If the "days" array is empty, write "No commits found for this period."
+- Use standard Markdown; no HTML.

gitglimpse-0.1.0/src/gitglimpse/commands/standup.md

@@ -0,0 +1,30 @@
+Generate a standup update from your recent git commits.
+
+Run the following shell command and capture its output:
+
+```
+glimpse standup --json
+```
+
+Then format the JSON result into a clean standup update using **exactly** this structure:
+
+```
+Standup — [date from JSON "date" field, formatted as "Month D, YYYY"]
+
+[For each entry in the "days" array:]
+[entry "label"]:
+- [task "summary"] ([task "branch" if non-empty], ~[estimated_minutes / 60 rounded to 1 decimal]h)
+
+Total estimated time: [total_estimated_hours]h
+```
+
+Rules:
+- Iterate the "days" array in order. Each day becomes its own section using the "label" field as the header (e.g. "Yesterday:", "Friday:", "Today:").
+- One bullet per task in each day's "tasks" array.
+- If a task has an empty "branch" field, omit the branch from the parenthetical.
+- If a task includes a "diff_snippet" field, use it to write a more accurate description of what was changed.
+- Do NOT add a "Today:" section with plans or next steps. Only show completed work from the data.
+- Do NOT invent tasks or work items that are not present in the JSON data.
+- Keep each bullet under 100 characters.
+- Use developer language: concise and direct.
+- If the "days" array is empty, write "(no commits found)".

gitglimpse-0.1.0/src/gitglimpse/commands/week.md

@@ -0,0 +1,35 @@
+Generate a weekly summary of your git activity.
+
+Run the following shell command and capture its output:
+
+```
+glimpse week --json
+```
+
+Then format the JSON result into a **weekly summary** using this structure:
+
+```
+Weekly Summary — [period.start to period.end, formatted as "Month D–D, YYYY" or "Month D – Month D, YYYY"]
+
+[For each entry in the "days" array that has tasks:]
+[day_name] ([date formatted as "Month D"]):
+- [task summary] (~[total_hours for task]h)
+Day total: [total_hours]h
+
+Key themes:
+- [3–5 bullet points identifying the main areas of work across the whole week,
+   inferred from task summaries and commit_messages]
+
+Highlights:
+- [1–3 notable accomplishments — largest change sets, most complex features, etc.]
+
+Week total: [week_total_hours]h across [total_tasks] tasks
+```
+
+Rules:
+- Only include days that appear in the "days" array (skip days with no commits).
+- Key themes and Highlights must be inferred from the actual data — do not invent.
+- Do NOT add a section with plans or next steps. Only summarize completed work.
+- Keep each theme/highlight bullet under 100 characters.
+- If the days array is empty, write "(no commits found this week)".
+- Use developer language: concise and direct.