Skip to main content
Manus에서 모든 스킬 실행
원클릭으로
GitHub 저장소

nix-agentic-tools

nix-agentic-tools에는 higherorderfunctor에서 수집한 skills 6개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.

수집된 skills
6
Stars
2
업데이트
2026-04-08
Forks
0
직업 범위
직업 카테고리 2개 · 100% 분류됨
저장소 탐색

이 저장소의 skills

stack-fix
소프트웨어 개발자

Use when you need to fix, correct, or update content in an earlier commit. Absorbs staged changes into correct stack commits INSTEAD of running git absorb or git commit --fixup via Bash. Prevents: missed dry-run preview, leftover staged changes going unnoticed, forgetting to restack. Falls back to guided manual amend when absorb cannot route hunks.

2026-04-08
stack-plan
소프트웨어 개발자

Use when you need to plan commits, restructure a stack, or commit uncommitted work as organized atomic commits. Builds a stack from a description, uncommitted work, or existing commits INSTEAD of manual git rebase -i, git reset --soft, or ad-hoc git move sequences. Prevents: wrong commit ordering, forward references, git move -F panics, untested intermediates.

2026-04-08
stack-split
소프트웨어 개발자

Use when you need to break up, split, or decompose a large commit into smaller atomic commits. Use INSTEAD of manual git rebase -i + edit or git reset HEAD^. Prevents: non-working intermediate commits, wrong split ordering, missed downstream restack.

2026-04-08
stack-submit
소프트웨어 개발자

Use when you need to push, submit, or create pull requests for a commit stack. Syncs, validates, and pushes INSTEAD of manual git sync + git submit + PR/MR creation. Handles branch creation, stacked PR/MR creation with correct base branches.

2026-04-08
stack-summary
소프트웨어 개발자

Use when you need to audit, analyze, or review stack quality before restructuring. Produces a structured summary with per-commit classification, philosophy audit, and violation flags. Output feeds directly into /stack-plan restructure mode. Use INSTEAD of manual git log inspection.

2026-04-08
stack-test
소프트웨어 품질 보증 분석가·테스터

Use when you need to run tests or formatters across every commit in a stack. Use INSTEAD of manual git test run or looping git checkout + test. Prevents: untested commits, wrong parallelism settings, cache misunderstandings.

2026-04-08