gitglimpse 0.1.0__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- gitglimpse/commands/report.md +33 -0
- gitglimpse/commands/standup.md +30 -0
- gitglimpse/commands/week.md +35 -0
- gitglimpse-0.1.0.dist-info/METADATA +23 -0
- gitglimpse-0.1.0.dist-info/RECORD +8 -0
- gitglimpse-0.1.0.dist-info/WHEEL +4 -0
- gitglimpse-0.1.0.dist-info/entry_points.txt +2 -0
- gitglimpse-0.1.0.dist-info/licenses/LICENSE +21 -0
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
Generate a detailed daily report from your git commits.
|
|
2
|
+
|
|
3
|
+
Run the following shell command and capture its output:
|
|
4
|
+
|
|
5
|
+
```
|
|
6
|
+
glimpse standup --json
|
|
7
|
+
```
|
|
8
|
+
|
|
9
|
+
Then format the JSON result into a **Markdown daily report** using this structure:
|
|
10
|
+
|
|
11
|
+
```markdown
|
|
12
|
+
# Daily Report — [date formatted as "Month D, YYYY"]
|
|
13
|
+
|
|
14
|
+
[For each entry in the "days" array:]
|
|
15
|
+
## [entry "label"] — [entry "date"]
|
|
16
|
+
|
|
17
|
+
[For each task in the day's "tasks" array:]
|
|
18
|
+
### [branch or "general"] — [commits] commit(s), ~[estimated_minutes/60 rounded]h
|
|
19
|
+
|
|
20
|
+
**Changes:** +[insertions] −[deletions]
|
|
21
|
+
|
|
22
|
+
[Plain-English description of what was accomplished, derived from the task summary
|
|
23
|
+
and commit_messages. 2–4 sentences max. Professional but direct.]
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
Rules:
|
|
27
|
+
- Iterate the "days" array in order. Each day becomes a level-2 section.
|
|
28
|
+
- One level-3 section per task within each day.
|
|
29
|
+
- Derive the description from "summary" and "commit_messages" — do not invent work.
|
|
30
|
+
- If insertions + deletions > 200, note it was a substantial change set.
|
|
31
|
+
- Do NOT add a section with plans or next steps. Only report completed work.
|
|
32
|
+
- If the "days" array is empty, write "No commits found for this period."
|
|
33
|
+
- Use standard Markdown; no HTML.
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
Generate a standup update from your recent git commits.
|
|
2
|
+
|
|
3
|
+
Run the following shell command and capture its output:
|
|
4
|
+
|
|
5
|
+
```
|
|
6
|
+
glimpse standup --json
|
|
7
|
+
```
|
|
8
|
+
|
|
9
|
+
Then format the JSON result into a clean standup update using **exactly** this structure:
|
|
10
|
+
|
|
11
|
+
```
|
|
12
|
+
Standup — [date from JSON "date" field, formatted as "Month D, YYYY"]
|
|
13
|
+
|
|
14
|
+
[For each entry in the "days" array:]
|
|
15
|
+
[entry "label"]:
|
|
16
|
+
- [task "summary"] ([task "branch" if non-empty], ~[estimated_minutes / 60 rounded to 1 decimal]h)
|
|
17
|
+
|
|
18
|
+
Total estimated time: [total_estimated_hours]h
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Rules:
|
|
22
|
+
- Iterate the "days" array in order. Each day becomes its own section using the "label" field as the header (e.g. "Yesterday:", "Friday:", "Today:").
|
|
23
|
+
- One bullet per task in each day's "tasks" array.
|
|
24
|
+
- If a task has an empty "branch" field, omit the branch from the parenthetical.
|
|
25
|
+
- If a task includes a "diff_snippet" field, use it to write a more accurate description of what was changed.
|
|
26
|
+
- Do NOT add a "Today:" section with plans or next steps. Only show completed work from the data.
|
|
27
|
+
- Do NOT invent tasks or work items that are not present in the JSON data.
|
|
28
|
+
- Keep each bullet under 100 characters.
|
|
29
|
+
- Use developer language: concise and direct.
|
|
30
|
+
- If the "days" array is empty, write "(no commits found)".
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
Generate a weekly summary of your git activity.
|
|
2
|
+
|
|
3
|
+
Run the following shell command and capture its output:
|
|
4
|
+
|
|
5
|
+
```
|
|
6
|
+
glimpse week --json
|
|
7
|
+
```
|
|
8
|
+
|
|
9
|
+
Then format the JSON result into a **weekly summary** using this structure:
|
|
10
|
+
|
|
11
|
+
```
|
|
12
|
+
Weekly Summary — [period.start to period.end, formatted as "Month D–D, YYYY" or "Month D – Month D, YYYY"]
|
|
13
|
+
|
|
14
|
+
[For each entry in the "days" array that has tasks:]
|
|
15
|
+
[day_name] ([date formatted as "Month D"]):
|
|
16
|
+
- [task summary] (~[total_hours for task]h)
|
|
17
|
+
Day total: [total_hours]h
|
|
18
|
+
|
|
19
|
+
Key themes:
|
|
20
|
+
- [3–5 bullet points identifying the main areas of work across the whole week,
|
|
21
|
+
inferred from task summaries and commit_messages]
|
|
22
|
+
|
|
23
|
+
Highlights:
|
|
24
|
+
- [1–3 notable accomplishments — largest change sets, most complex features, etc.]
|
|
25
|
+
|
|
26
|
+
Week total: [week_total_hours]h across [total_tasks] tasks
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
Rules:
|
|
30
|
+
- Only include days that appear in the "days" array (skip days with no commits).
|
|
31
|
+
- Key themes and Highlights must be inferred from the actual data — do not invent.
|
|
32
|
+
- Do NOT add a section with plans or next steps. Only summarize completed work.
|
|
33
|
+
- Keep each theme/highlight bullet under 100 characters.
|
|
34
|
+
- If the days array is empty, write "(no commits found this week)".
|
|
35
|
+
- Use developer language: concise and direct.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: gitglimpse
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: Analyze git history and generate standup updates, daily reports, and weekly summaries.
|
|
5
|
+
Project-URL: Homepage, https://github.com/dino/gitglimpse
|
|
6
|
+
Project-URL: Repository, https://github.com/dino/gitglimpse
|
|
7
|
+
Project-URL: Bug Tracker, https://github.com/dino/gitglimpse/issues
|
|
8
|
+
Author: Dino
|
|
9
|
+
License: MIT
|
|
10
|
+
License-File: LICENSE
|
|
11
|
+
Keywords: cli,developer-tools,git,standup
|
|
12
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
13
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
16
|
+
Requires-Python: >=3.11
|
|
17
|
+
Requires-Dist: inquirerpy>=0.3.4
|
|
18
|
+
Requires-Dist: platformdirs>=4.0
|
|
19
|
+
Requires-Dist: rich>=13.0
|
|
20
|
+
Requires-Dist: tomli-w>=1.2
|
|
21
|
+
Requires-Dist: typer[all]>=0.9.0
|
|
22
|
+
Provides-Extra: llm
|
|
23
|
+
Requires-Dist: httpx>=0.27; extra == 'llm'
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
gitglimpse/commands/report.md,sha256=21I1WQYCWnbdY-X2cDKHCSxicajkbpqIyvhUDiBCkbU,1175
|
|
2
|
+
gitglimpse/commands/standup.md,sha256=CL8HSAFRZr0GqqlgOa34efivm4XB0fGbygqLR--BucE,1240
|
|
3
|
+
gitglimpse/commands/week.md,sha256=d13s50k_QOxfijQ4pqPTCD-iuZiUs7A2vxia5uWf46U,1233
|
|
4
|
+
gitglimpse-0.1.0.dist-info/METADATA,sha256=xk1phv4IbZRaRI44GCoIRab4JkAxaFxk3icNADZTOfE,870
|
|
5
|
+
gitglimpse-0.1.0.dist-info/WHEEL,sha256=QccIxa26bgl1E6uMy58deGWi-0aeIkkangHcxk2kWfw,87
|
|
6
|
+
gitglimpse-0.1.0.dist-info/entry_points.txt,sha256=YxMQWzDKl3UEnzWNrGf_nmsG8Um9V3YgSooocTM8hVU,47
|
|
7
|
+
gitglimpse-0.1.0.dist-info/licenses/LICENSE,sha256=eojCoRhTAOL1ITzRV0x6OuJ62SB5iFXwUQdmEE_90m8,1065
|
|
8
|
+
gitglimpse-0.1.0.dist-info/RECORD,,
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 dinooo06
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|