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

agent-skills

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

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

이 저장소의 skills

external-grounding
소프트웨어 개발자

This skill should be used when implementation or review depends on external, version-sensitive facts: libraries, SDKs, APIs, CLIs, cloud services, security advisories, changelogs, release notes, or documentation that may have changed. It anchors local versions, ranks source quality, checks version fit and conflicts, and turns confirmed facts into implementation constraints before code changes.

2026-05-06
evidence-gated-review
소프트웨어 품질 보증 분석가·테스터

This skill should be used for unclear bugs, risky PR reviews, CI failures, flaky tests, security-sensitive changes, database or concurrency changes, external API changes, multi-file refactors, and investigations where claims need evidence before patching. It enforces an evidence-first Finding → Hypothesis → Review Claim → Defense → Probe → Decision → Patch → Verification → Handoff workflow so the agent does not jump to fixes, skip disconfirming checks, produce noisy review comments, or accept plausible but unverified explanations.

2026-04-29
execution-loop
소프트웨어 개발자

This skill should be used for authorized multi-step coding implementation work, including applying a plan, finishing a feature, implementing review feedback, or turning a specification into working code. It guides the agent through reading requirements and files, planning ordered units, making minimal edits, reviewing diffs, fixing findings, verifying with targeted and final checks, and committing only when explicitly authorized. Do not use it for trivial one-line edits or pure explanations.

2026-04-29
semantic-review
소프트웨어 품질 보증 분석가·테스터

This skill should be used when exploring an unfamiliar codebase or doing a full-file or full-module code review where surface-level scanning is insufficient. It forces per-symbol meaning analysis — what each function, type, branch, or module boundary intends to accomplish, what invariants it preserves, and why the code is shaped this way — before making implementation suggestions. Trigger when the user asks to "read", "review", "explore", "understand", "explain", "全文レビュー", "意味を分析", or "コード探索" in depth, or when implementation requires understanding existing code's purpose first. Intentionally expensive; the user chose this skill knowing that.

2026-04-29