DevSecOps Platform Lead Plan: Pull Request Gatekeeping for Security Agents

Role: Staff DevSecOps Engineer & Autonomous Quality Platform Lead

Context

• Target Repositories: {{repository_scope}}
• Enforced Security Standard: {{security_compliance_standard}}
• Static Analysis & Lint Ruleset: {{code_review_ruleset}}
• PR Blocking Conditions: {{blocking_criteria}}
• Feedback Delivery Channel: {{developer_feedback_channel}}
• Exempt Paths & Override Roles: {{exempted_code_paths}}

Task

Construct a comprehensive execution plan for an autonomous pull request reviewer agent that enforces {{security_compliance_standard}} across {{repository_scope}}, providing immediate actionable inline feedback and blocking non-compliant changes.

Method

1. Establish the agent scanning lifecycle upon pull request creation or update within {{repository_scope}}.
2. Map rules from {{code_review_ruleset}} to specific AST (Abstract Syntax Tree) patterns and secret-detection heuristics.
3. Filter out files matching {{exempted_code_paths}} while flagging any unauthorized modifications to critical security configurations.
4. Formulate the triage algorithm to classify identified code vulnerabilities against {{security_compliance_standard}}.
5. Define synthetic patch generation logic for common syntax and sanitation vulnerabilities that can be remediated safely.
6. Detail the gating mechanism that triggers automated merge blocks based on {{blocking_criteria}}.
7. Standardize formatted comment templates delivered directly to {{developer_feedback_channel}}.

Constraints

• Agent MUST block merging automatically when any condition in {{blocking_criteria}} is satisfied.
• Agent MUST NOT suggest inline code changes that introduce external third-party dependencies not already present in repository lockfiles.
• Secret detections must immediately redact sensitive values before publishing review comments.
• Scan duration target must remain below 120 seconds per standard PR.

Output format

Present the complete implementation plan containing:

1. Execution Pipeline Workflow (phase-by-phase chronological steps)
2. Policy Decision Matrix (risk tier, action taken, and merge status)
3. Automated Patch Generation Guidelines (criteria for proposing code changes)
4. Pull Request Review Output Template (Markdown template used by the agent in {{developer_feedback_channel}}) Length must be between 600 and 850 words.

Self-review

• Confirm all 6 context variables are actively utilized in the procedural steps.
• Check that merge blocking logic is explicit, deterministic, and unambiguous.
• Ensure feedback phrasing instructions emphasize developer clarity and minimal false-positive noise.