Skip to main content
Manus에서 모든 스킬 실행
원클릭으로
GitHub 저장소

split-trip

split-trip에는 pedrazamiguez에서 수집한 skills 10개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.

수집된 skills
10
Stars
2
업데이트
2026-07-09
Forks
0
직업 범위
직업 카테고리 2개 · 100% 분류됨
저장소 탐색

이 저장소의 skills

sp-address-pr-comments
소프트웨어 품질 보증 분석가·테스터

Address and resolve existing review comments on a GitHub pull request.

2026-07-09
sp-address-sonar-issues
소프트웨어 품질 보증 분석가·테스터

Fetch, analyze, and resolve SonarQube quality gate failures, code smells, bugs, and coverage gaps.

2026-07-09
sp-create-issue
소프트웨어 개발자

Turn an idea, problem description, or bug report into a well-formed GitHub issue and create it on GitHub once approved.

2026-07-09
sp-feasibility-study
소프트웨어 개발자

Study the feasibility and viability of a proposed feature or architectural change.

2026-07-09
sp-follow-up
소프트웨어 개발자

Request follow-up work on a specific issue (e.g. bug fixes, additional requirements, visual regression, or debugging) in a new or existing conversation without prior context.

2026-07-09
graphify
소프트웨어 개발자

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

2026-07-09
sp-plan-issue
소프트웨어 개발자

Plan a GitHub issue by investigating context and creating a detailed implementation plan. Present it to the user, and post it to the issue as a comment upon approval. No code changes.

2026-07-09
sp-replan-issue
소프트웨어 개발자

Revisit and revise a proposed implementation plan or solution for an issue using a different approach, architecture, or set of libraries, presenting it to the user for approval and updating the GitHub issue.

2026-07-09
sp-review-pr
소프트웨어 품질 보증 분석가·테스터

Review code changes on a pull request and evaluate against project constraints.

2026-07-09
sp-start-issue
소프트웨어 개발자

Implement a GitHub issue by strictly following the implementation plan posted on the issue.

2026-07-09