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

MichaelRBond

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

수집된 skills
4
저장소
1
업데이트
2026-04-14
저장소 지도

skills가 있는 위치

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

저장소 탐색

저장소와 대표 skills

spec-writer
프로젝트 관리 전문가

Create spec and implementation plan documents optimized for both human reviewers and AI coding agents. Use this skill whenever someone asks to write a spec, PRD, implementation plan, technical design document, project plan, or any planning document that will guide development work — especially work done by Claude Code or other AI coding agents. Also use when someone wants to restructure, reorganize, or improve an existing spec or planning document. Trigger on phrases like 'write a spec', 'create a plan', 'implementation document', 'break this into tasks', 'project planning', 'technical design', or when someone mentions their spec is too long, hard to review, or not working well with AI agents.

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

Review a GitHub PR using ACR (Agentic Code Reviewer), filter false positives, and produce a ready-to-post review. Reads PR context from $DEVDASH_CONTEXT when launched from devdash, or can be invoked manually.

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

Use when the user invokes /acr-review or asks to run the ACR review loop, external code review cycle, or iterative review process. Orchestrates an automated code review feedback loop using ACR (Agentic Code Reviewer). Never runs automatically.

2026-04-09
obsidian-planner
프로젝트 관리 전문가

Store planning documents, specs, architecture docs, meeting notes, task breakdowns, and other markdown artifacts in Obsidian via the Obsidian CLI -- so they sync across devices automatically. Use this skill whenever you would create a planning document, design doc, spec, specification, design spec, test spec, refactor spec, roadmap, ADR, sprint plan, meeting note, or any project-related markdown artifact. Also use when the user says "plan", "write a spec", "spec this out", "specification", "document this", "write up", "note this", "track this", "decision record", "save to obsidian", "sync to obsidian", or asks you to create any markdown file that is not source code. This includes ANY file that would otherwise go in a docs/, specs/, or design/ folder in the repo -- those files belong in Obsidian, not in the repo. Do NOT use this skill for README.md or other files that belong in the repo itself.

2026-04-01
저장소 1개 중 1개 표시
모든 저장소를 표시했습니다