submit-job

Automate SLURM job submission with dedup, git, and monitoring checks.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/KangOxford/auto-quant-research --skill submit-job
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submit-job
Source: https://github.com/KangOxford/auto-quant-research/tree/main/execution-layer/skills/submit-job
Command: npx skills add https://github.com/KangOxford/auto-quant-research --skill submit-job

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end SLURM submission workflow with built-in safety checks to prevent duplicates, dirty trees, and unsafe submissions.

Core Features & Use Cases

  • Dedup check to avoid job conflicts by scanning squeue before submission.
  • Commit check to prevent submitting with untracked or unstaged changes.
  • Config table printout for user confirmation and per-job parameter verification.
  • sbatch with a descriptive job name and resource parameters.
  • Append to live_jobs.md for traceability and post-submission record keeping.
  • Automatic post-submit monitoring hooks to observe job status and log progress.
  • Save monitor state to recover monitors after session reconnect.

Quick Start

Ensure a clean git state and run the submit-job workflow to perform dedup checks, commit, and submit the SLURM job.

Frequently Asked Questions about submit-job

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

FAQPage Schema
How do I automate SLURM job submission with duplicate checks and git safeguards?

Automating SLURM job submission with safeguards requires scanning squeue for duplicates, verifying a clean git state, printing config tables for confirmation, running sbatch with descriptive job names, appending to live_jobs.md, and launching background post-submit monitoring.

What is the best way to prevent submitting duplicate sbatch jobs in an HPC environment?

The best way to prevent duplicate sbatch jobs is running a pre-submission dedup check that scans squeue before submitting, ensuring new jobs do not conflict with existing queued or running tasks in the SLURM environment.

Does SLURM submission require a clean git tree before running sbatch?

While SLURM itself does not require a clean git tree, enforcing a commit check before sbatch submission prevents submitting jobs with untracked or unstaged changes, ensuring reproducibility and traceability across HPC batch runs.

How to monitor sbatch job status and log progress after SLURM submission?

To monitor sbatch job status after SLURM submission, launch a background post-submit monitoring workflow that observes job status, updates live logs, saves monitor state to files, and recovers monitors after session reconnects.

Can I use automated sbatch submission for HPC batch jobs with uncommitted code changes?

Automated sbatch submission with built-in commit checks blocks jobs when untracked or unstaged git changes exist, requiring you to commit or stash modifications before executing the SLURM submission workflow.