Add autofix-code-scanning-alert documentation to safe-outputs reference

[Copilot]

Add autofix-code-scanning-alert documentation to safe-outputs reference

• Review schema, implementation, and existing usage examples
• Add entry to "Security & Agent Tasks" section list
• Add detailed documentation section after "Code Scanning Alerts"
• Include parameters documentation (max, github-token)
• Add YAML configuration example
• Add usage notes and guidelines
• Verify markdown formatting and links
• Test documentation builds correctly
• Add repository scope specification to TOC entry for consistency
• Simplify documentation to match style of adjacent sections

Summary

Added concise documentation for the autofix-code-scanning-alert safe-output operation:

• Entry in TOC under "Security & Agent Tasks" with consistent formatting (max: 10, same-repo only)
• Simple documentation section matching the style of adjacent Code Scanning Alerts section
• YAML example showing max parameter configuration

The feature is now documented and discoverable in the safe-outputs reference.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Code Quality] Add autofix-code-scanning-alert documentation to safe-outputs reference</issue_title>
<issue_description>The autofix-code-scanning-alert safe-output operation is fully implemented and defined in the schema but is completely missing from the user documentation, preventing users from discovering and using this feature.

Source

Extracted from Safe-Outputs Comprehensive Audit discussion githubnext/gh-aw#12389

Problem

• ✅ Schema: Fully defined in pkg/parser/schemas/main_workflow_schema.json with complete parameter specification
• ✅ Implementation: Complete Go implementation in pkg/workflow/autofix_code_scanning_alert.go
• ❌ Documentation: Missing from docs/src/content/docs/reference/safe-outputs.md

Users cannot discover or use this feature because it's not documented in the safe-outputs reference.

Files Affected

• docs/src/content/docs/reference/safe-outputs.md - Add new section

Suggested Changes

Add a new section under "Security & Agent Tasks" category in the safe-outputs reference documentation with:

1. Description: Explain what autofix-code-scanning-alert does (creates automated fixes for code scanning alerts)
2. Parameters: Document all available parameters (from schema)
3. YAML Example: Show realistic usage example
4. Usage Notes: When to use vs other safe-output operations

Success Criteria

• Documentation section added to safe-outputs.md
• All parameters documented with descriptions
• At least one working YAML example included
• Documentation passes markdown linting
• Feature is discoverable in documentation search

Priority

High - Missing documentation prevents users from discovering an existing feature. Quick fix with high impact on feature adoption.

Estimated Effort

1-2 hours - Straightforward documentation task with existing schema and implementation as references.

AI generated by Discussion Task Miner - Code Quality Improvement Agent

• expires on Feb 12, 2026, 1:34 AM UTC

Comments on the Issue (you are @copilot in this section)

• Fixes [Code Quality] Add autofix-code-scanning-alert documentation to safe-outputs reference #12418

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pelikhan]

@copilot keep it simple

[Copilot]

Simplified documentation to match the style of the adjacent Code Scanning Alerts section. Removed detailed subsections and kept it concise. (e3bea71)