vdjdb-publish

Create and update GitHub issues for VDJdb data chunks.

155|28|Updated Jan 6, 2016
One-click install
npx skills add https://github.com/antigenomics/vdjdb-db --skill vdjdb-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vdjdb-publish
Source: https://github.com/antigenomics/vdjdb-db/tree/main/skills/vdjdb-publish
Command: npx skills add https://github.com/antigenomics/vdjdb-db --skill vdjdb-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

Manages the publication of VDJdb data chunks by creating or updating GitHub issues with each chunk, streamlining the process of data submission and integration.

Core Features & Use Cases

  • Automated Issue Creation: Automatically creates GitHub issues for each new or modified chunk of VDJdb data.
  • Chunk Commitment: Commits individual chunks with reference to the corresponding GitHub issue.
  • User Confirmation: Asks for user confirmation before creating issues or committing changes.
  • Use Case: Ideal for researchers and data curators managing large datasets in VDJdb and seeking to automate the process of data submission and issue tracking.

Quick Start

Run the /vdjdb-publish command from the root of the repository to process new or modified chunks in the 'chunks/' directory.

Frequently Asked Questions about vdjdb-publish

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

FAQPage Schema
How do I automate publishing VDJdb data chunks to GitHub issues?

You can automate publishing VDJdb data chunks to GitHub issues by running the vdjdb-publish command from the repository root. It processes new or modified files in the 'chunks/' directory, handles file naming conventions, and interacts with the GitHub API to create or update issues.

Do I need git and GitHub CLI to manage VDJdb data submissions?

Yes, you need both git and GitHub CLI installed to manage VDJdb data submissions. The automation relies on these dependencies to interact with the GitHub API for creating and updating issues and committing individual data chunks.

Can I review VDJdb chunks before they are committed to GitHub?

Yes, the tool asks for user confirmation before creating new issues or committing changes. This ensures you can review each VDJdb data chunk and verify the extracted PubMed IDs before the integration is finalized.

What is the best way to track large VDJdb datasets during publication?

The best way to track large VDJdb datasets is by automating issue creation for each chunk. This streamlines data submission by maintaining a direct reference between each committed chunk and its corresponding GitHub issue.

How does PubMed ID extraction work for VDJdb GitHub issues?

PubMed ID extraction works by parsing file naming conventions within the VDJdb chunks directory. The tool processes these identifiers automatically during the automated creation or updating of GitHub issues.

Why does my VDJdb chunk publication require the chunks directory?

VDJdb chunk publication requires the chunks directory because the command specifically targets new or modified files located within that folder to process, commit, and generate corresponding GitHub issues.