Engine Report

Three-Pillar Intelligence

Unlike standard AI commit generators that produce a single sentence, GitSage breaks every analysis into three distinct tactical sections — giving you a complete picture of every change.

Overview

When you run gitsage, the engine produces a structured report with three sections. Each targets a different audience and serves a different purpose.

bash

123456789101112131415

gitsage
# ╔══ GitSage Report ═══════════════════════════════════╗
# ║                                                      ║
# ║  🧠 What Changed                                     ║
# ║    Added JWT token expiry validation in middleware   ║
# ║                                                      ║
# ║  💡 Why it Matters                                   ║
# ║    Prevents stale sessions causing 401 errors        ║
# ║                                                      ║
# ║  🎯 Reach & Scope                                    ║
# ║    auth/middleware.py · core/session_manager.py      ║
# ║                                                      ║
# ║  Confidence: ████████████████████░░  91%             ║
# ╚══════════════════════════════════════════════════════╝

🧠

What Changed

A concise structural summary of the code modifications. GitSage extracts file paths, added/removed line counts, function signatures, and class-level changes from the raw git diff.

bash

1234567

# GitSage Report — What Changed
Modified: src/auth/middleware.py (+19, -0)
Added method: validate_token_expiry(token: str) -> bool
  - JWT decoding with expiry verification
  - Session invalidation on expired tokens
  - Warning logs for invalid token errors

💡

Why it Matters

The logical reasoning behind the change. GitSage infers business context from code structure, naming conventions, and diff patterns — providing the justification that reviewers and future developers need.

bash

12345

# GitSage Report — Why it Matters
Prevents stale sessions from remaining active beyond
JWT expiry, eliminating a class of 401 Unauthorized
errors in production. The automatic session invalidation
reduces support tickets from users stuck in bad auth states.

Stealth Active

Ollama Ready

🎯

Reach & Scope

Identification of all modules, classes, and files affected by the change. This helps catch unintended ripple effects and ensures nothing is missed in code review or testing.

bash

12345678

# GitSage Report — Reach & Scope
Primary:
  → src/auth/middleware.py        [modified]
Downstream impact:
  → src/core/session_manager.py   [calls invalidate_session]
  → src/utils/logger.py           [logging dependency]
  → tests/auth/test_middleware.py [test coverage required]

Confidence Score

Every suggestion includes a Confidence Score (0–100%). If confidence drops below 50%, GitSage will prompt you for manual input rather than committing an uncertain message.

[████████████████████░░]  91% — High confidence. Committing...

[██████████░░░░░░░░░░░░]  47% — Low confidence. Please review before committing.

[████░░░░░░░░░░░░░░░░░░]  18% — Very uncertain. Manual commit message required.

Full Confidence Score documentation

Next Steps

Configure GitSage Switch AI Providers