finding-format

Generate structured security finding reports with YAML frontmatter for CodeCome.

39|4|Updated May 6, 2026
One-click install
npx skills add https://github.com/pruiz/CodeCome --skill finding-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding-format
Source: https://github.com/pruiz/CodeCome/tree/main/.opencode/skills/finding-format
Command: npx skills add https://github.com/pruiz/CodeCome --skill finding-format

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a consistent framework for creating, reviewing, and managing vulnerability findings in CodeCome, ensuring clarity and traceability.

Core Features & Use Cases

  • Structured Report Generation: Defines templates for each finding with mandatory frontmatter fields to facilitate review and processing.
  • Consistent Naming and Classification: Enforces naming conventions and status tracking to maintain project integrity.
  • Use Case: Engineers document a new security issue with all required metadata, ensuring accurate status progression from pending to confirmed.

Quick Start

Use the finding-format skill to generate a new finding report with all required fields in YAML frontmatter, then fill in detailed vulnerability information in the sections.

Frequently Asked Questions about finding-format

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

FAQPage Schema
How do I structure a security vulnerability report in YAML frontmatter?

To document a security finding, generate a report with mandatory YAML frontmatter fields for classification and status, then fill the body sections with detailed vulnerability information and evidence.

What is the standard format for documenting CodeCome findings?

The standard format for documenting CodeCome findings uses a structured template with YAML frontmatter to enforce naming conventions, consistent classification, and accurate status progression from pending to confirmed.

How do I track the status of a vulnerability assessment from pending to confirmed?

Track vulnerability assessment status by utilizing mandatory metadata fields within the reporting template, which support consistent status progression and maintain traceability throughout the review process.

Can I use a standard template for security findings to ensure traceability?

Yes, using a standard template for security findings ensures traceability by providing a consistent framework with exact metadata fields for classification, evidence management, and review processing.

What metadata is required for creating a vulnerability report?

Required metadata for a vulnerability report includes mandatory YAML frontmatter fields for classification, status tracking, and evidence management, ensuring clarity and accurate progression during review.