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

$pwd:

verification

Name: Verification
Author: TechDufus

// Verifying implementation work before claiming completion; covers tests, affected artifacts, evidence, and unresolved risks.

Manus에서 실행

$ git log --oneline --stat

stars:403

forks:64

updated:2026년 5월 19일 02:49

SKILL.md

readonly

name	verification
description	Verifying implementation work before claiming completion; covers tests, affected artifacts, evidence, and unresolved risks.
condition	Use before saying work is done, complete, fixed, ready, verified, or when the user asks if something is done.

Verification playbook

Use this skill before claiming non-trivial work is complete.

Procedure

Identify the exact behavior or artifact changed.
Identify the narrowest meaningful verification command or scenario for that change.
Run it unless the needed dependency is genuinely unavailable.
Inspect the result; do not infer success from an unrelated build or lint.
Check directly affected artifacts: callsites, config, tests, docs, generated files, and cleanup of obsolete paths.
Report only observed evidence. Mark unverified claims explicitly.

Good evidence

A targeted unit or integration test covering changed behavior.
A role/playbook check that applies the changed role and confirms idempotence.
A CLI command that reads the exact managed config value or runtime behavior.
A reproduction command showing the original failure is gone.

Not enough by itself

Syntax check only.
A broad unrelated test suite that does not cover the change.
A successful file write or formatter run.
An assumption that config loaded because YAML looked valid.

related-skills.json

같은 저장소

work.md

from "TechDufus/dotfiles"

Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams.

2026-05-19403

commit.md

from "TechDufus/dotfiles"

Preparing and creating git commits when explicitly requested; covers staged diff review, secrets checks, and conventional commit messages.

2026-05-19403

commit.md

from "TechDufus/dotfiles"

Create a conventional commit from current workspace changes. Use when the user asks to run $commit, asks to commit changes, or asks for a commit message from the current diff.

2026-05-14403

github-issue-hierarchy.md

from "TechDufus/dotfiles"

Create GitHub issues with optional parent/sub-issue relationships and organization issue types. Use when the user asks to create, link, or retag GitHub issues, especially when they mention a parent issue, sub-issues, tasks, bugs, epics, or cross-repo issue hierarchy.

2026-04-09403

intent.md

from "TechDufus/dotfiles"

Extract the underlying intent behind a request, issue, PR, or diff. Focus on problem and desired outcome; do not propose implementation, testing strategy, or rollout plans.

2026-03-20403

skill-creator.md

from "TechDufus/dotfiles"

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

2026-01-09403

package.json

"author": "TechDufus"

"repository": "TechDufus/dotfiles"

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

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

소프트웨어 품질 보증 분석가·테스터컴퓨터 및 수학직15-1253L4

name	verification
description	Verifying implementation work before claiming completion; covers tests, affected artifacts, evidence, and unresolved risks.
condition	Use before saying work is done, complete, fixed, ready, verified, or when the user asks if something is done.

Verification playbook

Use this skill before claiming non-trivial work is complete.

Procedure

Identify the exact behavior or artifact changed.
Identify the narrowest meaningful verification command or scenario for that change.
Run it unless the needed dependency is genuinely unavailable.
Inspect the result; do not infer success from an unrelated build or lint.
Check directly affected artifacts: callsites, config, tests, docs, generated files, and cleanup of obsolete paths.
Report only observed evidence. Mark unverified claims explicitly.

Good evidence

A targeted unit or integration test covering changed behavior.
A role/playbook check that applies the changed role and confirms idempotence.
A CLI command that reads the exact managed config value or runtime behavior.
A reproduction command showing the original failure is gone.

Not enough by itself

Syntax check only.
A broad unrelated test suite that does not cover the change.
A successful file write or formatter run.
An assumption that config loaded because YAML looked valid.

verification

Verification playbook

Procedure

Good evidence

Not enough by itself

이 저장소의 다른 Skills

이 저장소의 다른 Skills

Verification playbook

Procedure

Good evidence

Not enough by itself