원클릭으로 Manus에서 모든 스킬 실행

시작하기

plan-issue

스타4

포크1

업데이트2026년 3월 10일 00:38

Plan the implementation of a GitHub issue

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

alexmond

alexmond/spring-boot-config-json-schema

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Plan implementation of issue #$ARGUMENTS

Step 1: Read the issue

gh issue view $ARGUMENTS

Step 2: Explore the codebase

Key places to check:

spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/ — main source
spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/service/ — core services
spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/jsonschemamodel/ — schema models
spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/metamodel/ — metadata models
spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/config/ — configuration
spring-boot-config-json-schema-starter/src/test/ — tests

Step 3: Write the plan

Create a detailed implementation plan:

What needs to change — list specific files and what changes are needed
New files — any new classes, configs, or tests needed
Testing strategy — what tests to add or modify
Risk assessment — what could break, edge cases to handle
Execution order — the sequence of changes

Step 4: Post the plan

Post the plan as a comment on the issue:

gh issue comment $ARGUMENTS --body "<plan>"

이 저장소의 다른 Skills

같은 저장소

codestyle

alexmond/spring-boot-config-json-schema

Project coding standards and conventions for Java 17 with Lombok, spring-javaformat, checkstyle, and PMD

2026-03-104

implement-issue

alexmond/spring-boot-config-json-schema

Implement a GitHub issue with branch and pull request workflow

2026-03-104

issue-track

alexmond/spring-boot-config-json-schema

Create or update a GitHub issue for tracking work

2026-03-104

jacoco

alexmond/spring-boot-config-json-schema

Check JaCoCo code coverage

2026-03-104

learn

alexmond/spring-boot-config-json-schema

Save a learning to project memory. Invoke automatically (without user asking) whenever a task required more than one fix cycle to resolve — e.g. a test failed and needed a second attempt, a compile error required a correction, an API behaved unexpectedly, or an assumption proved wrong mid-task. Also invoke when the user explicitly asks to remember something. Do NOT invoke for routine single-pass work.

2026-03-104

mvn-build

alexmond/spring-boot-config-json-schema

Build the project with Maven

2026-03-104

name	plan-issue
description	Plan the implementation of a GitHub issue
argument-hint	["issue-number"]
allowed-tools	Bash(gh *)

Plan implementation of issue #$ARGUMENTS

Step 1: Read the issue

gh issue view $ARGUMENTS

Step 2: Explore the codebase

Key places to check:

spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/ — main source
spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/service/ — core services
spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/jsonschemamodel/ — schema models
spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/metamodel/ — metadata models
spring-boot-config-json-schema-starter/src/main/java/org/alexmond/config/json/schema/config/ — configuration
spring-boot-config-json-schema-starter/src/test/ — tests

Step 3: Write the plan

Create a detailed implementation plan:

What needs to change — list specific files and what changes are needed
New files — any new classes, configs, or tests needed
Testing strategy — what tests to add or modify
Risk assessment — what could break, edge cases to handle
Execution order — the sequence of changes

Step 4: Post the plan

Post the plan as a comment on the issue:

gh issue comment $ARGUMENTS --body "<plan>"