cd /news/ai-tools/reckoning-github-feedback-companion · home topics ai-tools article
[ARTICLE · art-15055] src=github.com pub= topic=ai-tools verified=true sentiment=· neutral

Reckoning – GitHub Feedback Companion

GitHub user "Reckoning" released a client-side tool that compiles a user's pull requests, reviews, and issues into a structured self-review, with optional AI-generated summaries and analysis. The open-source companion runs entirely in the browser, sending GitHub personal access tokens and AI keys directly from the user's browser to the respective APIs without any backend or telemetry. The tool aims to help developers track and reflect on their contributions by generating headline accomplishments, themes, and STAR-format stories from their GitHub activity.

read3 min publishedMay 27, 2026

A client-side companion that turns your GitHub activity into a feedback-cycle self-review.

Pull every PR you authored, reviewed, or commented on, and every issue you opened or participated in within a date range. Then, optionally, point an AI provider at the data to generate a structured self-review with themes, headline accomplishments, and STAR stories — or ask freeform questions like "What auth work did I do?" or "Which PRs took longest to merge?"

Everything runs in your browser. No backend, no telemetry, no servers I control. Your GitHub PAT and AI key are sent directly from your browser to the respective APIs and nowhere else.

npm install
npm run dev

Open the URL Vite prints (usually http://localhost:5173

).

npm run build

The build emits a static site to ./dist

. Drop that folder onto any static host.

A ready-to-use Actions workflow lives at .github/workflows/deploy.yml

. To turn it on:

  • Push this repo to GitHub.
  • On GitHub: Settings → Pages → Build and deployment → Source: GitHub Actions. - Push to main

(or trigger the workflow manually). The action builds and publishes to Pages. - The site appears at https://<your-username>.github.io/<repo-name>/

.

The Vite config uses base: './'

so the build works from any subpath without configuration. A .nojekyll

is included so Pages doesn't strip files starting with _

.

Netlify / Vercel / Cloudflare Pages— point them at the repo, build commandnpm run build

, publish directorydist

Self-hostednpx serve dist

or any nginx/Caddy static config

Contributed— PRs you authored (is:pr author:USER

)Reviewed— PRs you formally reviewed or left comments on (reviewed-by:USER

commenter:USER

)Issues— Issues you opened or participated in (is:issue involves:USER

)

Each view shows a stat count, expandable cards, and direct links to GitHub.

When an AI key is present, each view gets a "Generate" button that produces:

  • Headline accomplishments with PR/issue links
  • 2–4 themes grouping related work
  • "By the numbers" paragraph
  • One STAR-format story for a standout item

Plus a global Q&A bar that answers freeform questions against all your cached contributions.

Anthropic(Claude Sonnet 4.5)** OpenAI**(GPT-4o)** Google**(Gemini 2.5 Pro)

Bring your own key for any of them.

Create a Personal Access Token with these scopes:

repo

— read your private repos and orgs (usepublic_repo

if you only need public access)read:org

— see contributions in org reposread:user

— read your own profile for the username fallback

A fine-grained PAT scoped to read-only on the orgs/repos you care about is the most secure option.

SSO orgs:If any of your orgs use SAML/SSO, go back to the[tokens page]after creating the token, clickConfigure SSOnext to it, and authorize each org. Without this, contributions in those orgs are silently missing from results.

No server. Everything is a static SPA. Your tokens go from your browser straight toapi.github.com

and your AI provider's API.Storage. Keys live insessionStorage

by default (cleared when the tab closes). The "Remember on this device" checkbox switches tolocalStorage

. The "Clear data" button on the setup screen wipes both.No analytics, no telemetry, no third-party JS beyond Google Fonts (loaded once at startup).

  • GitHub's search API caps results at 1,000 per query. For very long windows on a very active user, narrow the date range or filter by repo. - GraphQL is used wherever cheaper than REST, but a power-user query against many repos can still consume a few hundred rate-limit points. The progress screen shows your remaining quota.
  • AI calls truncate item descriptions to keep prompts compact. For very long PRs, follow the links in the AI's output for full context.
src/
  App.jsx                  ← Top-level orchestration of the four screens
  main.jsx                 ← Vite entry
  index.css                ← Tailwind + custom typography
  components/
    ui.jsx                 ← Shared primitives (Button, Input, Logo, Section)
    SetupScreen.jsx        ← Token entry + AI provider selection
    FilterScreen.jsx       ← Date range + repo type-ahead
    FetchProgress.jsx      ← Animated fetch progress
    ResultsScreen.jsx      ← Three-tab results + AI summaries + Q&A
  lib/
    storage.js             ← localStorage/sessionStorage wrapper
    github.js              ← GraphQL queries + pagination
    ai.js                  ← Provider-agnostic AI calls

MIT — do whatever you want with it.

── more in #ai-tools 4 stories · sorted by recency
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/reckoning-github-fee…] indexed:0 read:3min 2026-05-27 ·