Review playbook
PR Title Linter
Checks PR titles against Conventional Commits and suggests a compliant title.
When a pull request is opened, checks that its title follows the Conventional Commits format (e.g. 'feat(scope): summary'). If it doesn't, posts a single comment with a corrected suggestion inferred from the change. Advisory and quiet: it says nothing when the title is already fine.
- Identifier
pr-title-linter- Version
- 1.1.0
- Steps
- 3
- Triggers
- 2
- conventions
- pr
- lint
- automated
When it runs
pull_request.opened- Settle delay
- 5s after the event
Only when all hold
- pullRequest.isDraft not equals true
- actor.username not in dependabot, dependabot[bot], renovate, renovate[bot], github-actions, github-actions[bot]
- actor.username not contains [bot]
pull_request.reopened- Settle delay
- 5s after the event
Only when all hold
- pullRequest.isDraft not equals true
- actor.username not in dependabot, dependabot[bot], renovate, renovate[bot], github-actions, github-actions[bot]
- actor.username not contains [bot]
The pipeline
The graph below is the one the workflow opens with in the builder, same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01PR Opened / Reopened
triggerThe event that starts the run.
- 02Lint PR Title
agent.runOne agent works the task with its toolkit.
- 03Publish PR Title Linter Report
report.publishPosts or updates a deduplicated report comment.
The agent
PR Title Linter
- Base type
- Senior Developer
- Temperature
- 0.1
- Max iterations
- 12
- Tools
- 2
Git provider · 1
get_pull_request_diffGet Pull Request Diff · read
Status · 1
update_statusUpdate Status · write