fork

Fork scanned upstreams into a disclosure org and file draft advisories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Staging scanned upstreams into a disclosure org, enabling private vulnerability reporting on the fork, and organizing draft security advisories for each finding to streamline collaboration with the relevant team.

Core Features & Use Cases

  • Fork the upstream into the designated fork_org, enable private vulnerability reporting on the fork, and attach a scan note to the upstream commit for traceability.
  • Create draft advisories on the fork for any qualifying findings, invite the appropriate org team as collaborators, and preserve a clean audit trail without touching the upstream repo.
  • Re-run safely by re-using existing fork and notes, skipping already filed advisories or non-ready findings.

Quick Start

Stage the scanned repository into the disclosure org and begin drafting advisories for each finding after a scan completes.

Frequently Asked Questions about fork

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

FAQPage Schema
How do I create draft security advisories on a GitHub fork after a scan?▼

To create draft security advisories on a GitHub fork, this Skill stages the scanned upstream into a disclosure org and files one draft advisory per finding. It uses the GitHub CLI to manage repository operations and invites the relevant org team as collaborators.

How do I enable private vulnerability reporting on a forked repository?▼

Enabling private vulnerability reporting on a forked repository is handled automatically during the staging process. The Skill forks the upstream into a designated disclosure org and configures private vulnerability reporting to manage findings securely.

What is the best way to manage vulnerability disclosures without modifying the upstream repo?▼

Managing vulnerability disclosures without modifying the upstream repo is achieved by forking the upstream into a disclosure org. The Skill files draft advisories and records scan notes on the fork, preserving a clean audit trail while leaving the original repository untouched.

What happens if I re-run the advisory filing workflow on an already scanned repository?▼

Re-running the advisory filing workflow on an already scanned repository is safe. The Skill re-uses existing forks and notes, skips advisories that have already been filed, and ignores findings that are not yet ready for disclosure.

Can I use the GitHub CLI to invite organization teams as collaborators on security advisories?▼

Yes, you can use the GitHub CLI to invite organization teams as collaborators on security advisories. The Skill creates a draft advisory for each finding and automatically invites the appropriate org team to collaborate on the disclosure.

How does recording a scan as a note on a fork improve vulnerability traceability?▼

Recording a scan as a note on a fork improves vulnerability traceability by attaching the scan results to the upstream commit. This ensures that draft advisories filed in the disclosure org maintain a clear link to the original scan data.