원클릭으로 Manus에서 모든 스킬 실행

submit-task

스타7

포크1

업데이트2026년 5월 17일 22:13

Guides AI through the end-to-end task submission workflow for the claude-config repo: (1) initializing a task workspace with new_task.sh, (2) committing and pushing to v2 and main branches, (3) deploying to the remote GPU server via ssh. Trigger when user says 'submit', 'push', 'deploy', 'version bump', 'push to main', or asks to commit and push changes to this repo.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

gyy0592

gyy0592/claude-config

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

submit-task — 任务提交与部署流程

Step 1 — 创建任务 workspace（如果还没有）

bash /home/yguo173/Programs/claude-config/scripts/new_task.sh \
  --name <task_name> \
  --goal "..." \
  --constraint "..."

如果 new_task.sh 已在 PATH（运行过 set_claude.sh）：

new_task.sh --name <task_name> --goal "..." --constraint "..."

Step 2 — 版本号更新（如果是新 release）

更新 hooks/stop_bg_aware.sh 第 2 行 # stop_bg_aware.sh — v2.X.Y 的版本号
不需要单独的 VERSION 文件

Step 3 — Commit

cd /home/yguo173/Programs/claude-config
git add -p   # 或 git add <specific files>
git commit -m "v2.X.Y: <one-line description>"

Step 4 — Push 到 v2 分支

git push origin v2

Step 5 — Merge 到 main 并 push

git checkout main
git merge v2
git push origin main
git checkout v2   # 回到工作分支

Step 6 — 部署到远端服务器

ssh awesome-gpu-name "cd /path/to/claude-config && git pull && bash set_claude.sh"

如果不知道远端路径，先 ssh 进去查：

ssh awesome-gpu-name "find ~ -name set_claude.sh 2>/dev/null | head -3"

注意事项

git push origin main 是 对外可见操作，确认改动正确再执行
ssh 部署前确认远端 git pull 能拉到最新 main
如果远端路径不对，set_claude.sh 会报错退出（有 health check）

이 저장소의 다른 Skills

같은 저장소

plain-language

gyy0592/claude-config

Enforces just-in-time term definition in technical writing — every name / file path / acronym / black-box term gets explained the moment it first appears (one line, parenthetical, inline), and re-explained whenever it reappears after a long gap. **NEVER** front-load a glossary at the top of a document; **NEVER** assume the reader has already read 100 turns of context. Trigger this skill aggressively whenever (1) the user complains 'I don't understand / 听不懂 / 说人话 / 给我说人话 / 你在说啥 / 这是啥 / 黑话 / 别用术语 / 操你妈的看不懂', (2) the user pushes back on a previous reply with 'what is X' / 'what does X mean' / '这个 X 是什么', (3) you're writing any technical report / diagnosis / plan / postmortem / architecture doc that mentions internal file paths, scripts, hooks, FSM states, variable names, or any term that wasn't in the user's original prompt verbatim, (4) you're about to write a 'Glossary' or 'Definitions' section at the top of a document — STOP, this skill says don't. Over-trigger rather than under-trigger; the cost of one extra

2026-05-177

efficiency-audit

gyy0592/claude-config

Audits whether the current code is already running at maximum speed by checking GPU/CPU/IO bottleneck saturation. Red-alarms if NONE of GPU/CPU/IO is bottlenecked — that proves speedup is mathematically possible and the code is wasting compute. Loads 5 sub-skills progressively. Trigger this skill aggressively whenever the user asks about speed, performance, throughput, latency, "why is this slow", "is my code optimal", "can I make this faster", "find the bottleneck", profiling, optimization, GPU utilization, dataloader speed, training speed, inference speed, 性能, 加速, 瓶颈, 慢, 优化, 训练慢, 推理慢, even when the user doesn't explicitly use the word "audit". Also trigger when reviewing training scripts, inference scripts, or any data-processing pipeline for efficiency. Skip only if the user clearly asks about correctness, not speed.

2026-05-127

no-undefined

gyy0592/claude-config

Document-level rigour auditor. Enforces that every term, symbol, abbreviation, experimental label, and formula appears with its definition adjacent to its first occurrence — and re-states it on distant reuse. Also enforces no-step-skipping in math derivations. Invoke whenever writing or reviewing a technical report, paper explanation, or derivation where a reader could encounter an undefined token. Pairs with math-explain (single-formula checklist) and zero-jump-check (inter-step seam auditor) as the outer document-level layer of the rigorous-writing stack.

2026-05-127

code-tree

gyy0592/claude-config

Generate a structured, navigable code documentation document for a Python codebase — the 'code tree'. Use this skill whenever the user asks to document a codebase, explain how the code works end-to-end, generate a code tree, write code documentation, understand call chains, or map out how functions relate to each other. Trigger on: '生成代码树', '代码树', '给我写代码文档', '解释代码结构', '画一个调用树', 'generate a code tree', 'document the codebase', 'write code docs', 'explain how the code works', 'map out the call chains', 'code documentation'. The output is a single Markdown file with: (1) directory tree, (2) ASCII call trees per functional area, (3) per-function docs with always-visible input/output descriptions and collapsed technical details. After generating, the skill runs ask-claude to verify format quality and fixes issues.

2026-04-297

gen-draft-simplify

gyy0592/claude-config

Generate a project-specific draft_simplify.md for a code repository — a high-level plan for an upcoming maintainability refactor that preserves runtime behavior bit-for-bit. Use this skill whenever the user wants to PLAN a code-cleanup / refactor / maintainability pass on a whole repository, before any code is changed. Trigger aggressively on phrases like '生成simplify draft', '写一下化简方案', '重构方案', '生成可维护性化简的draft', '帮我规划一下重构', 'plan a refactor', 'draft a simplify plan', 'generate a refactor plan for this repo'. The skill does NOT execute the refactor — it only produces the planning document. The output is a single instantiated draft_simplify.md at the repo root, with all placeholders filled from a mandatory AskUserQuestion intake. Do NOT trigger for: single-PR review (use /simplify), one-shot small edits, or when the user explicitly asks to start refactoring immediately. Do NOT confuse with /gen-draft (which is the generic draft generator) — this skill is specialized: the output draft already contains the full si

2026-04-287

this-cluster-general

gyy0592/claude-config

Reference card for a single-node SLURM GPU server. General template — fill in all {{PLACEHOLDER}} values in FILL_IN.md before use. Use when the user invokes /this-cluster-general, or automatically before: running local commands on this box, submitting/cancelling SLURM jobs, writing sbatch scripts, choosing a Python interpreter, deploying code locally, or reading job logs. Also consult when other skills need local machine facts. Triggers on: /this-cluster-general, sbatch, squeue, scancel, sinfo, SLURM, 本机, 这台机子, 这台服务器, 提交任务, 跑实验, gpu partition, 本地部署, 本地提交.

2026-04-287

name	submit-task
description	Guides AI through the end-to-end task submission workflow for the claude-config repo: (1) initializing a task workspace with new_task.sh, (2) committing and pushing to v2 and main branches, (3) deploying to the remote GPU server via ssh. Trigger when user says 'submit', 'push', 'deploy', 'version bump', 'push to main', or asks to commit and push changes to this repo.

submit-task — 任务提交与部署流程

Step 1 — 创建任务 workspace（如果还没有）

bash /home/yguo173/Programs/claude-config/scripts/new_task.sh \
  --name <task_name> \
  --goal "..." \
  --constraint "..."

如果 new_task.sh 已在 PATH（运行过 set_claude.sh）：

new_task.sh --name <task_name> --goal "..." --constraint "..."

Step 2 — 版本号更新（如果是新 release）

更新 hooks/stop_bg_aware.sh 第 2 行 # stop_bg_aware.sh — v2.X.Y 的版本号
不需要单独的 VERSION 文件

Step 3 — Commit

cd /home/yguo173/Programs/claude-config
git add -p   # 或 git add <specific files>
git commit -m "v2.X.Y: <one-line description>"

Step 4 — Push 到 v2 分支

git push origin v2

Step 5 — Merge 到 main 并 push

git checkout main
git merge v2
git push origin main
git checkout v2   # 回到工作分支

Step 6 — 部署到远端服务器

ssh awesome-gpu-name "cd /path/to/claude-config && git pull && bash set_claude.sh"

如果不知道远端路径，先 ssh 进去查：

ssh awesome-gpu-name "find ~ -name set_claude.sh 2>/dev/null | head -3"

注意事项

git push origin main 是 对外可见操作，确认改动正确再执行
ssh 部署前确认远端 git pull 能拉到最新 main
如果远端路径不对，set_claude.sh 会报错退出（有 health check）