close-codescan

Close GitHub Code Scanning alerts with justification and audit logging.

84|5|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/fitlab-ai/agent-infra --skill close-codescan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close-codescan
Source: https://github.com/fitlab-ai/agent-infra/tree/main/.agents/skills/close-codescan
Command: npx skills add https://github.com/fitlab-ai/agent-infra --skill close-codescan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Closes open Code Scanning alerts by recording a valid justification and updating audit logs.

Core Features & Use Cases

  • Automated alert closure with status validation and API mapping
  • Audit-ready logging that captures closure details and task updates
  • Use Case: When a Code Scanning alert is a false positive, already resolved, or not applicable, close it with proper rationale and preserve an audit trail.

Quick Start

Close Code Scanning alerts by providing a justification and letting the skill perform validation, API calls, and logging.

Frequently Asked Questions about close-codescan

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

FAQPage Schema
How do I close GitHub code scanning alerts with a valid justification?

To close GitHub code scanning alerts, you provide a valid justification such as false positive or already resolved. The skill validates the required fields, maps the request to the GitHub Code Scanning API, and updates audit logs to preserve the closure record.

What is the best way to automate closing false positive code scanning alerts in batch?

Batch closing of false positive code scanning alerts is supported within repository security governance workflows. The skill performs status validation, maps the provided justifications to the GitHub API, and generates audit-ready logging for each closed alert.

Does closing code scanning alerts automatically generate audit logs for repository security governance?

Yes, closing code scanning alerts generates audit-ready logging that captures detailed closure records. This ensures repository security governance workflows preserve a complete audit trail of the justification and task status updates for every alert.

Can I use this approach to close code scanning alerts that are already resolved or not applicable?

Yes, you can close code scanning alerts when they are already resolved or not applicable. The skill requires a valid rationale for the closure, performs status validation, and records the details in the audit logs to maintain compliance.

What happens if required fields are missing when closing GitHub code scanning alerts?

Closing GitHub code scanning alerts requires specific fields, particularly a valid justification. The skill enforces these required fields before mapping the closure request to the GitHub Code Scanning API, preventing incomplete audit records.

Why does closing code scanning alerts require recording a justification?

Recording a justification when closing code scanning alerts is required to maintain an audit-ready trail. It documents why an alert was marked as a false positive or not applicable, ensuring repository security governance workflows remain compliant and transparent.