Skip to main content
Run any Skill in Manus
with one click
ebkn
GitHub creator profile

ebkn

Repository-level view of 7 collected skills across 1 GitHub repositories.

skills collected
7
repositories
1
updated
2026-07-21
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

repository explorer

Repositories and representative skills

init-project
software-developers

Scaffold a new project in the current directory — git init, README.md, CLAUDE.md, AGENTS.md, Claude settings.json, linter/test config, unused-code detection (knip for TypeScript), runtime pin, lockfile (npm for TypeScript, uv for Python), supply-chain hardening (SHA-pinned GitHub Actions, least-privilege GITHUB_TOKEN, Dependabot cooldown, pinned container base images), and CI (GitHub Actions + Dependabot) for the specified language (TypeScript, Go, Python), plus optional Next.js boilerplate with error boundaries, security headers, SEO, and a health endpoint. Use this skill when the user wants to initialize or bootstrap a new project from scratch, set up a fresh repo, or scaffold project boilerplate.

2026-07-21
commit
software-developers

Stage and commit changes with conventional commits

2026-07-03
create-pr
software-developers

Create a GitHub pull request with context-aware description

2026-07-03
deep-dive
project-management-specialists

A relentless interview to think a topic through before committing — software requirements or any general question (a decision, a concept, a plan, research). Act as a critical thinking partner: surface the real intent, challenge assumptions, weigh alternatives, name what stays uncertain. One question at a time, each with a recommended answer. Always end by writing a document capturing what was decided and what is open. Use proactively whenever the user wants to think something through, define requirements, or clear up ambiguity — triggered by "要件定義したい", "深掘りしたい", "壁打ちしたい", "一緒に考えて", "help me think this through", "grill me", or the `/deep-dive` command.

2026-07-03
review-support
software-quality-assurance-analysts-and-testers

Help the reviewer understand a GitHub pull request through dialogue. Start with a short orientation to the PR's purpose and approach, then answer their questions and dig into the real code interactively so their understanding deepens. Only once understanding is solid — and only when the reviewer asks — organize their own conclusions into review notes they send themselves. Facilitator: never produce ok/ng verdicts or review comments on your own. Triggered by requests like "PRをレビューしたい", "PRを理解したい", "このPRを見たい", "help me review this PR", or the `/review-support` command.

2026-07-03
review-test
software-quality-assurance-analysts-and-testers

テストコードのレビューを行う。公開契約(入出力・エラー契約・副作用保証)を起点に、テストが振る舞いの仕様として機能しているかを評価し、改善点を優先度付きで報告する。「テストをレビューして」「テストのレビューをお願い」「test review」「review the tests」などテストそのもののレビューを依頼された時、または /review-test コマンドで起動する。

2026-07-03
update-pr
software-developers

Update an existing GitHub pull request after adding commits by revising title/body, preserving template format, and pushing pending branch changes.

2026-07-03
Showing 1 of 1 repositories
All repositories loaded