autosnippet-batch-scan

Extract Cursor-driven recipe candidates from targets and submit them for review.

2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/GxFn/AutoSnippet --skill autosnippet-batch-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autosnippet-batch-scan
Source: https://github.com/GxFn/AutoSnippet/tree/main/skills/autosnippet-batch-scan
Command: npx skills add https://github.com/GxFn/AutoSnippet --skill autosnippet-batch-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables batch extraction of Cursor-driven, Recipe-like candidates from a Target and submits them to the Dashboard for human review, streamlining scalable code guidance.

Core Features & Use Cases

  • Target-driven batch scanning: fetch a list of targets and their files, then extract multiple, single-scenario items per file.
  • Per-file itemization: ensure each candidate corresponds to one specific usage pattern, resulting in multiple independent Recipes for a single file when needed.
  • Flow to Dashboard: submit candidates via autosnippet_submit_candidates and review them in the Dashboard Candidates page.
  • Use Case: Imagine scanning a large library to rapidly generate and vet lightweight, reusable code patterns for common tasks across files.

Quick Start

Initiate MCP and Cursor integration, then run the batch flow: get_targets, get_target_files, extract per-file items, and submit_candidates, monitoring the Dashboard for reviews.

Frequently Asked Questions about autosnippet-batch-scan

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

FAQPage Schema
How do I extract reusable code patterns from multiple files using Cursor?

Batch scan targets with Cursor to generate recipe-like candidates by fetching files, extracting independent usage patterns per file, and submitting them via autosnippet_submit_candidates for Dashboard review.

What is a recipe candidate in code scanning and when do I need it?

A recipe candidate is a single-scenario, reusable code pattern extracted from a target file. You need batch scanning when processing large libraries to rapidly generate and vet multiple independent recipes across files.

Do I need MCP tooling to run batch scans and submit candidates?

Yes, batch scanning requires MCP tooling and explicit Cursor integration to execute the workflow of fetching targets, retrieving files, extracting items, and submitting candidates to the Dashboard.

What's the best way to automate code pattern extraction across an entire target?

Use a batch scanning flow to fetch a target and its files, extract per-file usage patterns into independent items, and submit them via autosnippet_submit_candidates for Dashboard review.

Can I generate multiple independent recipes from a single file during batch scanning?

Yes, per-file itemization ensures each candidate corresponds to one specific usage pattern, resulting in multiple independent recipes for a single file when needed.

Where do I review the candidates generated from a target batch scan?

You review generated candidates in the Dashboard Candidates page after submitting them via the autosnippet_submit_candidates function during the batch scanning workflow.