lead-agent

Automate PR creation, review, and merge workflows with Azure DevOps and ADR tracking.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/clouseryan/agentic-skills --skill lead-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lead-agent
Source: https://github.com/clouseryan/agentic-skills/tree/main/dev-team/lead
Command: npx skills add https://github.com/clouseryan/agentic-skills --skill lead-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Centralizes and enforces the PR lifecycle for software projects, ensuring PR creation, review, and merging occur under governance and auditable processes.

Core Features & Use Cases

  • PR Creation and assignment with clear descriptions
  • Full code-review protocol execution during PR reviews
  • PR Approval / Rejection and merging with enforced policies
  • Security gate checks and traceability via ADRs for decision context

Quick Start

Ask the Lead Engineer to create a PR from the current branch targeting main.

Frequently Asked Questions about lead-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request creation and code reviews in Azure DevOps?

Automating pull request creation and code reviews in Azure DevOps requires orchestrating PR lifecycle management to handle assignments, structured review protocols, and merge policies. This ensures governance and traceability for software teams using Git workflows.

What is PR lifecycle governance and why do software teams need it?

PR lifecycle governance is the centralized enforcement of pull request creation, code review protocols, and merging under auditable processes. Software teams need it to ensure security gate checks and traceable change leadership before integrating code into main branches.

How do I enforce security gates and track decisions during a PR review?

Enforcing security gates and tracking decisions during a PR review involves executing structured review protocols and recording architectural decision records for context. This provides traceable change leadership and ensures all security checks pass before merging.

Does this PR automation work for individual developers or only team workflows?

PR automation applies to both individual developers and teams using Git workflows with Azure DevOps. It satisfies requirements for mandatory PR creation, structured review protocols, and traceable change leadership as defined in team standard operating procedures.

Can I use lead-agent to manage pull request merges with enforced policies?

Managing pull request merges with enforced policies is supported by automating PR approval, rejection, and merging processes. It applies security gate checks and ensures ADR tracking for decision context before final integration.

What are the limitations of automating code review governance for pull requests?

Automating code review governance is limited to Git workflows specifically using Azure DevOps and ADR tracking. It requires adherence to team SOPs for mandatory PR creation and structured review protocols, meaning teams outside this ecosystem cannot leverage its traceability features.