Getting Started

KittyLog uses AI to turn your GitHub activity into polished, reader-friendly changelogs — automatically. Add a repo, pick a schedule or trigger, and KittyLog summarizes commits, groups changes, and publishes to a hosted page.

1

Connect GitHub

Click "Connect GitHub" on the homepage. KittyLog uses GitHub OAuth — no separate account or password needed.

2

Add a Changelog

Open the Changelogs page and click "Add Changelog". A step-by-step wizard walks you through selecting a repository, choosing a generation trigger (daily, weekly, monthly, on tag push, or on GitHub release), configuring schedule or filter settings, and customizing your changelog style.

3

Backfill & Go

If your repo already has releases or tags, KittyLog offers to generate changelogs for them right away. After that, new changelogs are created automatically based on your chosen mode.

Connected changelogs on the dashboard
The Changelogs page with connected repos and the Add Changelog button
Repository selection in the Add Changelog modal
Selecting a repository in the Add Changelog modal

Changelog Modes

KittyLog can generate changelogs on a schedule, on tag push, or when you publish a GitHub Release. Pick the mode that matches your release workflow — you can change it anytime from each repository's settings.

Scheduled

Recommended

Automatically generate a changelog on a daily, weekly, or monthly schedule summarizing all changes since the last generation.

Runs on your chosen schedule - Only generates if new commits exist

On Git Tag Push

Generate a changelog whenever you push a new Git tag. Useful for projects that use tags without GitHub Releases.

Triggered by: Git tag push (e.g., v1.0.0, release-2024-01)

On GitHub Release

Generate a changelog whenever you publish a GitHub Release. Perfect for projects with versioned releases and formal release workflows.

Triggered by: GitHub Release publish event

Changelog trigger mode settings
Trigger mode and schedule configuration in repository settings

Writing Style Presets

Control the tone, detail level, and formatting of your changelogs. These settings are configured per-repository so each project can have its own voice.

Preset

Users — non-technical, focused on what changed from the end-user perspective. Developers — includes technical context like affected modules and APIs. Custom — write your own system prompt for full control over output.

Technical Language

Plain, Balanced, or Technical. Controls how much jargon and implementation detail appears.

Verbosity

Brief, Normal, or Detailed. Determines how much each change is elaborated on.

Emoji Use

Off, Subtle, or Expressive. Adds visual markers to category headings and list items.

Category Style

Friendly (What's New, Improvements, Bug Fixes) or Technical (Added, Changed, Fixed, Security).

Changelog style presets and advanced options
Writing style presets and advanced options in repository settings

Advanced Options

Fine-tune what context the AI uses when generating changelogs. These options are available on Pro plans and above.

Include Code Diffs

Pass git diffs to the AI for richer, more accurate summaries. May increase generation time.

Include PRs & Issues

Pull in PR descriptions and linked issues for additional context. Useful for repos with detailed PR workflows.

Review Before Publishing

Changelogs stay as drafts until you approve them. Edit the content before it goes live on your public page.

Ignore Patterns

Skip changelog generation for specific tag patterns. This applies to both Release and Tag modes — KittyLog won't generate a changelog when a matching tag or release is detected.

Common Patterns to Ignore

nightly
beta
alpha
rc
canary
dev
snapshot
pre

How It Works

When a tag or release matches any of your ignore patterns, KittyLog will skip changelog generation entirely. Pattern matching is case-insensitive and checks if the pattern appears anywhere in the tag name.

v1.0.0 → Changelog generated

v1.0.0-beta.1 → Skipped (matches "beta")

v2.0.0-nightly.123 → Skipped (matches "nightly")

Ignore pattern configuration
Ignore pattern presets and custom pattern input

Tip: You can also add custom patterns beyond the presets — useful for project-specific conventions like test- or wip-.

Backfill Past Releases

Already have a history of releases or tags? KittyLog can generate changelogs for anything that happened before you connected.

On Connect

When you first connect a repository in Release or Tag mode, KittyLog detects existing releases/tags and offers to generate changelogs for them right away.

From the Repository Page

Open any connected repository and expand "Backfill Changelogs" to see entries that are missing. What shows up depends on your mode: past releases (Release mode), past tags (Tag mode), or past time periods (Scheduled mode). Select the ones you want and generate them in bulk.

Backfill past releases
Missing entries available for bulk generation

Tip: Items that already have changelogs are automatically hidden from the backfill list.

GitHub Integration

KittyLog connects through the GitHub App install flow — no tokens to manage or webhooks to configure manually. Everything is set up automatically when you connect a repository.

Webhook Events

KittyLog registers webhooks to listen for the events that trigger changelog generation:

  • release — published GitHub Releases (Release mode)
  • create — new git tags (Tag mode)
  • push — new commits (Scheduled mode uses this to know when there's something to summarize)

Hosted Changelog Page

Every connected repo gets a hosted changelog at kittylog.app/c/owner/repo. This is a public, shareable page with a share button and an optional README badge. On the Business plan, readers can translate any changelog into one of 16 supported languages on-demand. You can also point a custom domain at it (see Sharing & Custom Domains).

Permissions

KittyLog requests the minimum permissions needed:

  • Code & commits (read) — to analyze changes
  • Metadata & releases (read) — to detect events
  • Contents (write, optional) — only needed if you enable auto-commit of CHANGELOG.md to your repo
Connected repository settings
A connected repository with links to its changelog, GitHub page, and settings tabs

Notifications

Get notified when changelogs are generated, when generation fails, or when you're approaching your monthly quota. Notifications can be configured globally or overridden per-repository.

Email

Available on all plans. Sent to your GitHub email by default, or configure a custom address in Settings → Notifications. Email covers all event types: generation success, failure, and quota warnings.

Discord

Post changelog updates to a Discord channel with rich embeds showing the repository, version, and summary. Just paste a webhook URL into Settings → Notifications — the setup guide is shown inline.

Per-Repository Overrides

Each repository's settings page has a Notifications tab where you can toggle email and Discord independently — useful for silencing noisy test repos while keeping alerts on your main projects.

Notification settings
Email and Discord webhook configuration in notification settings

Plus feature: Discord notifications require a Plus plan or higher. Email notifications are available on all plans including Free.

Sharing & Custom Domains

Every connected repository gets a hosted changelog page. The Sharing tab in your repository settings controls how that page is accessed and branded.

Hosted URL & Visibility

Your changelog is published at kittylog.app/c/owner/repo. Toggle visibility to make it public or restrict access.

Vanity Links

Create a short, memorable URL like kittylog.app/your-project instead of the default owner/repo path. Available on Plus plans and above.

README Badge

Add a changelog badge to your GitHub README with one line of Markdown or HTML. Choose from Flat, Flat Square, Plastic, and For the Badge styles — the snippet is generated for you in the Sharing tab.

Custom Domain

Point your own domain (e.g., changelog.yoursite.com) at your changelog. Setup requires two DNS records:

CNAMEchangelog → kittylog.app
TXT_kittylog.changelog → kittylog-verify-xxxxx

SSL is provisioned automatically after DNS verification.

Sharing and custom domain settings
Sharing tab with visibility, vanity links, README badge, and custom domain settings

Pro feature: Custom domains require a Pro plan (up to 3 domains) or Business plan (unlimited). DNS propagation can take up to 24–48 hours.

Pricing & Limits

Each "generation" is one changelog entry — a single release, tag, or scheduled period. All plans include unlimited generations and backfills.

🐣Early Bird Pricing Active🐣

Lock in these discounted rates forever! Your subscription price won't change even after early bird ends.

Free

$0/month

  • 1 public repository
  • Unlimited generations
  • Hosted changelog page

Plus

$5/month$10

  • 5 repositories
  • Private repos included
  • Unlimited generations
  • Discord notifications
  • Vanity links

Pro

Popular

$15/month$25

  • 25 repositories
  • 3 custom domains
  • Include diffs & mentioned PRs/issues
  • Review before publish

Business

$99/month$149

  • Unlimited repositories
  • Everything in Pro
  • Unlimited custom domains
  • Remove KittyLog branding

Annual billing available with 2 months free.