Skip to main content
Manus에서 모든 스킬 실행
원클릭으로
kommundsen
GitHub 제작자 프로필

kommundsen

1개 GitHub 저장소에서 수집된 12개 skills를 저장소 단위로 보여줍니다.

수집된 skills
12
저장소
1
업데이트
2026-05-09
저장소 지도

skills가 있는 위치

수집된 skill 수가 많은 주요 저장소와 이 제작자 카탈로그 내 비중, 직업 분포를 보여줍니다.

저장소 탐색

저장소와 대표 skills

make-release
소프트웨어 개발자

Run the full release preparation checklist for Conjecture: promote PublicAPI files, update CHANGELOG, run tests, run benchmarks, update api-baseline DLLs, then output the commit message and tag commands. Use whenever the user wants to cut a new release. Triggers on "make-release", "prepare release", "cut a release", or "/make-release <version>".

2026-05-09
benchmark
소프트웨어 품질 보증 분석가·테스터

Create or run a BenchmarkDotNet benchmark for Conjecture components. Use this skill whenever the user wants to measure performance, check throughput, compare two implementations, scaffold a benchmark class, or investigate memory allocations — even if they don't say "BenchmarkDotNet" explicitly. Triggers on phrases like "benchmark X", "how fast is", "measure performance of", "run benchmarks", "compare baseline vs candidate", or "check allocations".

2026-04-28
port
소프트웨어 개발자

Port a Python Hypothesis module to idiomatic C# for the Conjecture project. Use this skill whenever the user wants to translate, adapt, or port code from the Python Hypothesis library into C# — even if they don't say "port" explicitly. Triggers on phrases like "port X from hypothesis", "translate this Python module", "implement X based on hypothesis", "bring over the hypothesis shrinking logic", or when referencing a specific Python Hypothesis file or module to add to Conjecture.

2026-04-28
scaffold
소프트웨어 개발자

Scaffold a new .NET project or module with correct structure for the Conjecture solution. Use this skill whenever the user wants to add a new project, test project, module, or set up the solution from scratch — even if they don't say "scaffold" explicitly. Triggers on phrases like "add a new project", "create a module for", "set up a test project for", "add X to the solution", or any request to create new .NET structural components in the repo.

2026-04-28
ideation
경영 분석가

Articulate, interrogate, and record an idea on a GitHub Discussion thread before it becomes a concrete enhancement issue. Two modes: with a discussion ref, interrogate the thread and propose follow-up comments; without a ref, collaborate on a first draft, post it to the Ideas category, then offer to enter interrogation mode. Use this skill whenever the user wants to brainstorm, develop, or pressure-test an idea, or says things like "I have an idea about X", "let's brainstorm Y", "ideate on Z", "interrogate discussion #N", "develop the idea in #N", or "I want to think through X".

2026-04-26
implement
소프트웨어 개발자

Drive an entire GitHub enhancement issue to completion as one feature branch and one PR, looping through its sub-issues as TDD cycles (each committed individually). Use this skill when the user wants to ship a coherent multi-sub-issue enhancement as a single reviewable PR. Triggers on phrases like "implement enhancement #N", "work through all of #N", "drive #N to done on one branch", "one PR for the whole enhancement", or "implement #N end-to-end".

2026-04-26
plan-idea
소프트웨어 개발자

Promote a fully-interrogated and researched GitHub Discussion thread into a parent enhancement issue plus linked sub-issues, ready for `implement`. Synthesizes the discussion's idea, decisions, and research findings into the parent body, then reuses steps 7–9 of `plan-issue` (sub-issue design, creation, tasklist) — skipping the decision/question interrogation since `ideation` and `research-idea` already resolved them. Final stage of the chain `ideation` → `research-idea` → `plan-idea`. Use this skill whenever the user wants to graduate a Discussion into actual work, create the enhancement issue from a discussion, or says things like "promote discussion #N to an issue", "plan idea #N", "turn #N into issues", or "/plan-idea #N".

2026-04-26
research-idea
소프트웨어 개발자

Research a GitHub Discussion-resident idea against the codebase and prior art, then post a structured "Research findings" comment back to the thread. Spawns Explore agents for codebase reconnaissance and WebSearch for external prior art (Hypothesis, FsCheck, QuickCheck, papers, etc.). Middle stage of the chain `ideation` → `research-idea` → `plan-idea`. Use this skill whenever the user wants to validate the feasibility of an idea, gather prior art, or check what already exists in the codebase before committing to a plan. Triggers on phrases like "research discussion #N", "is idea #N feasible", "look up prior art for #N", "what's already in the codebase for #N", or "/research-idea #N".

2026-04-26
이 저장소에서 수집된 skills 12개 중 상위 8개를 표시합니다.
저장소 1개 중 1개 표시
모든 저장소를 표시했습니다