WhyLog - Decision Capture installs statistics

WhyLog captures the reasoning behind every pull request so your team always knows why code was written, not just what changed. Stop losing context when engineers leave, onboard new devs in days not weeks, and build a searchable knowledge base of every engineering decision your team has ever made.

Capabilities

• Automatically monitor pull requests and capture decision context • Route PR summaries to Slack for one-click team approval • Semantic search across all past engineering decisions • Generate branded PDF exports of decision logs • Multi-channel Slack workspace support

Benefits

• Eliminate Context Loss: When engineers leave or switch teams, the

reasoning behind every decision stays in WhyLog not in someone's head.

• Faster Onboarding: New engineers understand the codebase in days,

not weeks, by reading the decisions that shaped it.

• Searchable Decision History: Find out why any architectural choice

was made using natural language semantic search.

• Zero Friction: Works through your existing GitHub PR workflow

no new tools for your team to learn.

Getting Started

Requirements:

• A GitHub repository (public or private) • A Slack workspace (for decision routing) • Plan: Starter (Free), Team ($29/mo), Growth ($79/mo) • Availability: Generally Available

Setup Process:

• Install WhyLog and connect your GitHub repository • Connect your Slack workspace for PR notifications • WhyLog begins monitoring PRs automatically approve or edit

captured decisions directly from Slack

Example Use Cases

• "Why did we switch from REST to GraphQL in the auth service?" • "What was the reasoning behind removing the caching layer?" • "Show me all architectural decisions made in Q1" • "Why is this component built this way?"

Description from the GitHub Marketplace listing.