Tagger Setup Guide

Install it once and get pull request complexity, risk, and change-type context automatically.

Ready to Use

Tagger needs almost no setup and starts analysing pull requests as soon as the app is installed.

How It Works

Tagger analyses each pull request and posts a GitHub-native summary with review signal the team can use immediately.

Triggers

Analysis runs automatically when:

  • A pull request is opened
  • New commits are pushed to an open PR
  • A closed PR is reopened

What Tagger posts

Each PR comment includes:

Complexity Score (0-10)

An algorithmic score based on files changed, line counts, file types, and how spread out the change is.

  • 0-3: Low complexity (documentation, minor fixes)
  • 4-6: Medium complexity (features, refactoring)
  • 7-10: High complexity (major features, architecture changes)

Risk Level

A color-coded review signal based on complexity and file patterns:

  • LOW - Safe for quick review
  • MEDIUM - Standard review recommended
  • HIGH - Thorough review required

Note: PRs that only touch documentation files (.md, README, docs/) are automatically treated as lower-risk changes with reduced complexity scores.

Auto-Generated Tags

Tags inferred from the PR title, description, and file patterns:

featurebugfixdocumentationrefactortestsecurityperformancedependencies

Change Summary

  • Total files modified
  • Lines added and deleted
  • File type breakdown (TypeScript, Python, CSS, etc.)
  • Language distribution

Example Comment

## PR Analysis Summary

![Risk Level](https://img.shields.io/badge/Risk-MEDIUM-yellow)
![Complexity](https://img.shields.io/badge/Complexity-6/10-blue)
![Files Changed](https://img.shields.io/badge/Files-8-informational)

### Change Metrics
| Metric | Value |
|:-------|------:|
| Lines Added | +234 |
| Lines Deleted | -67 |
| Files Modified | 8 |
| Complexity Score | 6/10 |
| Risk Assessment | MEDIUM |

### Classification
`feature` `frontend` `typescript`

### Files by Type
**typescript**  5 files
**css**         2 files
**json**        1 file

---
Analysed by **Woden Tagger**

Privacy

Data Stored

  • GitHub account ID and organisation name
  • Installation timestamp and repository list
  • Basic analytics (PRs analysed, timestamps)

Data NOT Stored

  • Source code or file contents
  • PR descriptions or comments
  • Commit messages or diffs
  • Any sensitive or proprietary information

Tagger reads pull request metadata from GitHub to produce its analysis summary. No source code is stored.

Questions or Issues?

Tagger is a free tool. If you hit problems or want to request changes, open an issue on our GitHub repository.