Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/Morrison-Lab/ai-config --skill next명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | next |
| description | Insert after in-flight task. |
| user-invocable | true |
| allowed-tools | [] |
/next <instructions> means: finish what you're doing now, then do this
before anything else that's queued. It slots a task immediately after the
currently in-progress task — jumping the rest of the queue, but not interrupting
work already in flight.
It sits between its siblings in the queue family:
/first — head of queue; may pause in-progress work to run now./next — immediately after the current (in-progress) task./before <target> — immediately before the referenced queued task./also — tail of queue./last — sticky tail; stays last even as new /also tasks arrive.The user types /next followed by one or more instructions, e.g.:
/next once this refactor is done, run the tests before moving on/next after the current edit, tweak the table styling/next handle this right after, ahead of the other queued items/first)./next task immediately after, ahead of everything else still
queued./next task ran ahead of the rest of the queue./next is effectively
"do it now" — start it as the current task./nexts. The most recent /next slots immediately after the
current task; earlier /nexts follow it (LIFO right behind the current task),
all still ahead of the older /also queue./next task is tightly related to the current one. Common case —
it's fine to fold it into the same work unit (e.g. same file, same render) as
long as the current task's result is verified first./next still waits for it; if the user wanted
to interrupt, they'd use /first.