Fix small formatting issues

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

CHANGEME

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct
    • The when to get approval handbook section explains when DRI approval is required
    • The who can approve handbook section explains how to identify the DRI
    • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
    • The approver may merge the MR. If they approve but don't merge, you can merge.
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Update file _index.md

  • Changes Field to Regional through RM HB Page

  • Link the new RFH template into the api team handbook page

  • Add Source Code AI Prompts page

  • Update primary approver for Ecosystem

  • Add SLA for RCA for GitLab.com incidents

  • Sales Prospecting and Playbook - Updates links for Regional Marketing

  • fix: Add spaces to restore formatting

  • Update file knowledge-features-roadmap.md

  • Add cdaminato-gl to ecosystems team page

  • added feedback

  • Add schedule for monthly doc version releases to clarify TW assignments

  • feat: Update Security Configuration Profiles design doc with scanning contexts

  • Remove ai prompts page

  • Updates to the Regional Marketing HB page - MR 4

  • fix expansion

  • adding Office hours link

  • Remove the L&R Workflows placeholder from the Support Workflows page

  • Mktgops - 20250901-20250915

  • creating office hours page

  • Create Runner Core and CI Functions Platform pages

  • Removing team member, correcting manager

  • Update Payment Capture Guide FAQ

  • Continued Updates to RM Handbook

  • Update manager toolkit loa info.md

  • Add debug statements

  • Update to lead scoring

  • updated 7183

  • Updated with Completed and Active/Blocked

  • Add Ryan Lehmann to Monthly Maintenance schedule for April 2026

  • Added Thiru and removed leavers

  • Updates

  • Fixes names of Compliance Labs

  • Update design pairs

  • Fixed linting issues

  • Apply 1 suggestion(s) to 1 file(s)

Co-authored-by: Adil Farrukh afarrukh@gitlab.com

  • Apply 1 suggestion(s) to 1 file(s)

Co-authored-by: Adil Farrukh afarrukh@gitlab.com

  • Apply 1 suggestion(s) to 1 file(s)

Co-authored-by: Nate Rosandich nrosandich@gitlab.com

  • Apply 1 suggestion(s) to 1 file(s)

Co-authored-by: Nate Rosandich nrosandich@gitlab.com

  • Apply 1 suggestion(s) to 1 file(s)

Co-authored-by: Nate Rosandich nrosandich@gitlab.com

  • Thanks for the

  • Fix markdown linting errors in secure/_index.md

  • Convert all asterisk list items (*) to dash list items (-)
  • Fix MD004 unordered list style errors
  • Ensure consistent markdown formatting

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Remove duplicate AI prompts files
  • Remove duplicate ai-prompts/_index.md file
  • Remove duplicate software-supply-chain-security/ai-prompts.md file
  • Keep only main ai-prompts.md at section level
  • All other files now reference the single source of truth

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Remove Feedback and Iteration section completely
  • Remove remaining Feedback and Iteration section from AI prompts
  • Remove process owner and related issue metadata
  • Clean file structure with 17 comprehensive AI prompts
  • Fix markdown linting issues

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Remove Feedback and Iteration section and last update mention
  • Remove Feedback and Iteration section from AI prompts
  • Remove last updated date and process owner information
  • Clean up file structure for better maintainability
  • Keep 17 comprehensive AI prompts for all Sec Section teams

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Make team references generic for all Sec Section teams
  • Replace specific Software Supply Chain Security team references with generic terms
  • Update all context sections to use 'security features, vulnerability management, compliance, and security tooling'
  • Make AI prompts truly applicable to all Sec Section teams
  • Ensure prompts work for Application Security Testing, Security Risk Management, and Software Supply Chain Security teams

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Remove Security Documentation Review Prompt
  • Remove Security Documentation Review Prompt section from AI prompts
  • Update table of contents to remove the prompt entry
  • Update success criteria and usage guidelines
  • Update count from 18 to 17 AI prompts across all Sec section pages
  • Fix markdown linting issue with extra blank line

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Remove Quick Reference section from AI prompts
  • Remove entire Quick Reference section with categorized prompt recommendations
  • Simplify AI prompts documentation structure
  • Keep table of contents as the main navigation method
  • Maintain all 18 AI prompts and their detailed descriptions

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Remove Security Incident Response Prompt
  • Remove Security Incident Response Prompt section from AI prompts
  • Update table of contents to remove the prompt entry
  • Update Quick Reference section to remove incident response reference
  • Update success criteria and usage guidelines
  • Update count from 19 to 18 AI prompts across all Sec section pages
  • Remove incident response from prompt descriptions

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Rename AI prompts to ai-prompts.md for clarity
  • Move from ai-prompts/_index.md to ai-prompts.md
  • Update all links across Sec section pages to point to new location
  • Make AI prompts file more discoverable and accessible
  • Maintain all content and functionality

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Remove remaining Software Supply Chain Security stage references
  • Update all remaining 'GitLab's Software Supply Chain Security stage' references
  • Replace with generic 'Sec Section teams' terminology
  • Ensure all prompts are truly generic for all Sec teams
  • Maintain only appropriate reference in overview section

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Make AI prompts generic for all Sec Section teams
  • Update all prompts to be generic and applicable to all Sec teams
  • Replace Software Supply Chain Security specific references with Sec Section
  • Update context sections to reference security features, vulnerability management, compliance, and security tooling
  • Make prompts relevant to Application Security Testing, Security Risk Management, and Software Supply Chain Security teams
  • Ensure consistent terminology across all 19 AI prompts

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Move AI prompts to shared Sec section location
  • Move ai-prompts.md to shared location at /handbook/engineering/development/sec/ai-prompts/
  • Update title and description to reflect all Sec Section teams
  • Update all links across Sec section pages to point to shared location
  • Remove old ai-prompts.md from Software Supply Chain Security directory
  • Enable cross-team access to AI prompts from centralized location

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Add AI prompts links to Sec section and all stages
  • Add AI Prompts section to main Sec section page
  • Add AI Prompts section to Application Security Testing stage
  • Add AI Prompts section to Security Risk Management section
  • Link to comprehensive AI prompts documentation for all teams
  • Enable cross-team access to 19 documented AI prompts

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Add SAST False Positive Detection prompts
  • Add SAST False Positive Detection prompt for automatic false positive identification
  • Add SAST Vulnerability Triage prompt for vulnerability prioritization and remediation
  • Add Security Tooling Optimization prompt for tool configuration and performance
  • Update table of contents with new SAST & Security Tooling Prompts section
  • Update success criteria and usage guidelines to include SAST prompts
  • Based on Automatic Detection of SAST False Positives epic #17883

Related to: https://gitlab.com/groups/gitlab-org/-/epics/17883

  • Add Security Duo Agentic Tools experiment prompts
  • Add Vulnerability Management Analysis prompt for vulnerability reports and remediation
  • Add Compliance Management Assessment prompt for compliance audits and assessments
  • Add Security Policy Management prompt for policy creation and enforcement
  • Add Security Experiment Analysis prompt for experiment evaluation and scaling
  • Update table of contents with new Security Experiments & Advanced Prompts section
  • Update success criteria and usage guidelines to include new prompts
  • Based on Security Duo Agentic Tools epic #18115 experiments

Related to: https://gitlab.com/groups/gitlab-org/-/epics/18115

  • Add comprehensive table of contents for AI prompts
  • Add detailed table of contents with links and references
  • Include Security-Focused Prompts and Team Management & Process Prompts sections
  • Add Quick Reference section with categorized prompt recommendations
  • Include use cases, expected impact, and frequency for each prompt
  • Fix markdown linting issues with proper list formatting

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Add Sprint Planning and Onboarding AI prompts for SSCS teams
  • Add Sprint Planning Optimization prompt for better estimation and capacity planning
  • Add Onboarding Documentation Generator prompt for new engineer onboarding
  • Update success criteria and usage guidelines to include new prompts
  • All prompts tailored specifically for Software Supply Chain Security workflows
  • Addresses AI Transformation Initiative #19 requirements with 6 total prompts

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • Add AI prompts for Software Supply Chain Security teams
  • Create comprehensive AI prompts documentation for security workflows
  • Include prompts for security code review, vulnerability analysis, compliance auditing, incident response, and security testing
  • Add link to AI prompts in main SSCS index page
  • Addresses AI Transformation Initiative #19 requirements

Related to: https://gitlab.com/gitlab-org/ai-engineering/ai-transformation/-/issues/19

  • CICD Minor Lab Fix

Merge request reports

Loading