What problem does it solve? Creating pull requests in the n8n repository requires strict adherence to the check-pr-title CI validation rules, and malformed titles or incomplete PR bodies cause CI failures and review delays. ## Core Features & Use Cases - Conventional PR Titles: Generates titles in the type(scope): summary format with correct types, scopes, capitalization, and breaking-change markers. - Structured PR Bodies: Builds PR descriptions from the repository template including summary, related Linear tickets and GitHub issues, and the review checklist. - Security Fix Sanitization: Audits branch names, commits, titles, and test names so security fixes never expose the attack vector in public artifacts. - Use Case: After committing a bug fix on a feature branch, ask for a PR and receive a draft pull request with a validated title like fix(core): Resolve memory leak in execution engine, a complete body, and an optional collapsible implementation plan section. ## Quick Start Ask the assistant to create a pull request for the current branch and it will analyze the changes, format a compliant title, and open a draft PR using the gh CLI.