triage

Classify new repositories and enqueue quality scans via the scrutineer API.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill triage-lukehinds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/lukehinds/scrutineer-attest-test/tree/main/skills/triage
Command: npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill triage-lukehinds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically kick off the standard set of quality scans when a repository is added, and produce a concise summary of what was enqueued to guide follow-on checks and tuning.

Core Features & Use Cases

  • Orchestrates the default Scrutineer scan suite in parallel for a freshly-added repository.
  • Writes a short report summarizing enqueued work to report.json.
  • Allows editing the default coverage by adjusting the list in SKILL.md without touching core code.

Quick Start

Start by adding a repository to trigger the default triage workflow and review the generated report.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate security scans when a new repository is added to a pipeline?

Automating repository triage runs a brief scan to detect languages and package managers, then enqueues the appropriate quality scans automatically. It classifies the newly added repository and writes a concise summary of the enqueued work to report.json.

What is repository triage and how does it decide which scans to run?

Repository triage evaluates a new codebase by running a brief check to determine code and package presence. Based on the detected languages and package managers, it decides which specific scans to enqueue via the scrutineer API for that commit.

How do I stop duplicate automated scans from running on the same commit?

The triage process prevents duplicate automated scans by checking the scrutineer API status before enqueuing. It explicitly skips services that are already running or completed for the current commit, ensuring only necessary scans are dispatched.

Can I change the default scan coverage for new repositories without modifying code?

You can adjust default scan coverage by editing the scan list directly in SKILL.md. This allows you to tune which scans are enqueued for newly added repositories without needing to touch or modify the core implementation code.

What reporting output is generated when automating scans for a fresh repository?

Automating scans for a fresh repository generates a minimal report structure written to report.json. This concise file summarizes all the triage work that was enqueued, guiding any necessary follow-on checks or configuration tuning.