Skip to main content
Run any Skill in Manus
with one click
DmNote-App
GitHub creator profile

DmNote-App

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

skills collected
7
repositories
1
updated
2026-07-02
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

agent-plan
software-developers

작업 전 독립 서브에이전트(Opus)와 협업하여 구현 계획을 수립. 작업 계획, 설계 논의, 접근 방식 검토 시 사용.

2026-07-02
agent-review
software-quality-assurance-analysts-and-testers

작업 완료 후 독립 서브에이전트(Opus)를 활용한 적대적 코드 리뷰. 변경사항 리뷰, 코드 품질 검토, 최종 커밋 전 필수 리뷰에 사용.

2026-07-02
agent-debug
software-developers

버그 원인 추적 및 수정을 위한 메인 + 독립 서브에이전트(Opus) 협업 디버깅. 에러/증상 분석, 재현, 원인 특정, 회귀 디버깅 시 사용.

2026-07-02
codebase-memory-exploring
software-developers

This skill should be used when the user asks to "explore the codebase", "understand the architecture", "what functions exist", "show me the structure", "how is the code organized", "find functions matching", "search for classes", "list all routes", "show API endpoints", or needs codebase orientation.

2026-03-09
codebase-memory-quality
software-developers

This skill should be used when the user asks about "dead code", "find dead code", "detect dead code", "show dead code", "dead code analysis", "unused functions", "find unused functions", "unreachable code", "identify high fan-out functions", "find complex functions", "code quality audit", "find functions nobody calls", "reduce codebase size", "refactor candidates", "cleanup candidates", or needs code quality analysis.

2026-03-09
codebase-memory-reference
software-developers

This skill should be used when the user asks about "codebase-memory-mcp tools", "graph query syntax", "Cypher query examples", "edge types", "how to use search_graph", "query_graph examples", or needs reference documentation for the codebase knowledge graph tools.

2026-03-09
codebase-memory-tracing
software-developers

This skill should be used when the user asks "who calls this function", "what does X call", "trace the call chain", "find callers of", "show dependencies", "what depends on", "trace call path", "find all references to", "impact analysis", or needs to understand function call relationships and dependency chains.

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