Skip to main content

implementation

Start an implementation task with proper planning, TDD workflow, and session hand-off. Use when beginning work on a Jira issue, starting a new feature, or resuming implementation work. Triggers on phrases like "start task", "begin implementation", "work on issue", or "implement feature".

소스 정보

저장소
snyk/snyk-intellij-plugin
최근 소스 활동
2026년 2월 21일 08:45
감지된 SKILL.md 언어
영어
스타
69
포크
36

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
implementation
description
Start an implementation task with proper planning, TDD workflow, and session hand-off. Use when beginning work on a Jira issue, starting a new feature, or resuming implementation work. Triggers on phrases like "start task", "begin implementation", "work on issue", or "implement feature".
# Start Implementation Task ## Workflow Overview ``` Check Plan → [Create if missing] → TEST FIRST → Implement → Test & Lint → Commit → Session Hand-off ``` **TDD is NON-NEGOTIABLE**: Every code change requires a failing test BEFORE implementation. ## Phase 1: Initialize ### 1.1 Get Issue Context ```bash # Extract issue ID from branch git branch --show-current ``` The `issueID` follows format `XXX-XXXX` (e.g., `IDE-1718`). ### 1.2 Check for Implementation Plan Look for: `${issueID}_implementation_plan/${issueID}_implementation_plan.md` **If plan exists:** Read it, note current progress, continue from last checkpoint. **If no plan:** use skill `create-implementation-plan` to create one --- ## Phase 1: Planning ### Analysis - **Files to modify:** [list files] - **Files to create:** [list files] - **Packages affected:** [list packages] ### Flow Diagrams See: `docs/diagrams/${issueID}_*.png` --- ## Phase 2: Implementation (TDD) ** read and use testing skill for TDD instructions ** ### Steps - [ ] Step 1: [description] - [ ] Step 2: [description] - [ ] Step 3: [description] --- ## Phase 3: Review - [ ] All tests pass (`./gradlew test`) - [ ] Integration tests pass (`./gradlew verifyPlugin`) - [ ] Linting clean (`./gradlew ktlintCheck spotlessApply`) - [ ] Security scan clean (snyk_code_scan, snyk_sca_scan) - [ ] Documentation updated --- ## Progress Tracking | Step | Status | Notes | | ------ | ------- | ----- | | Step 1 | pending | | --- ## Session Log ### Session 1 - [DATE] **Started:** [time] **Completed:** [list of completed items] **Next:** [next steps for hand-off] --- ### Create Diagrams Create mermaid files `${issueID}_*.mmd` ### Get Confirmation **Stop here.** Present the plan and wait for user confirmation before proceeding. ## Phase 3: Implementation (Outside-In TDD) ### CRITICAL: TDD is MANDATORY **NEVER write production code before writing a failing test.** This applies to: - New features - Bug fixes - Security fixes - Refactoring - ANY code change ### TDD Gate Check ** ALWAYS use the testing skill. ** Before writing ANY production code, verify: - [ ] **Test exists?** Have I written a test for this change? - [ ] **Test fails?** Does the test fail without my change? - [ ] **Test is specific?** Does the test target the exact behavior I'm changing? **If ANY answer is NO → STOP and write the test first.** ### TDD Cycle For each feature/change: 1. **STOP** - Do not touch production code yet 2. **READ and USE testing skill.** 2. **Write failing test first** (outside-in: ensure smoke tests. also write unit tests) 3. **Run test** - confirm it fails for the right reason 4. **Write minimal code** to ./gradlew test pass 5. **Run test** - confirm it passes 6. **Refactor** if needed (tests must still pass) ### Commands ```bash # Run unit tests ./gradlew test # Run smoke tests ./gradlew verifyPlugin # Format and lint ./gradlew ktlintCheck spotlessApply ``` ### Progress Updates Before each step: ```markdown ## Progress Tracking | Step 1 | **in-progress** | Started [time] | ``` After each step: ```markdown ## Progress Tracking | Step 1 | **completed** | Finished [time] | ``` ## Phase 4: Finalize ### 4.1 Run All Tests ```bash ./gradlew test INTEG_TESTS=1 ./gradlew test ./gradlew verifyPlugin ``` All tests must pass. Fix any failures before proceeding. ### 4.2 Lint ```bash ./gradlew ktlintCheck spotlessApply ``` Zero linting errors required. Fix any issues. ### 4.3 Security Scan Run before commit: - `snyk_code_scan` with absolute project path - `snyk_sca_scan` with absolute project path Fix any security issues (except in test data). ### 4.4 Generate & Update Docs Update documentation in `./docs` as needed. ### 4.5 Commit Pre-commit checklist: - [ ] Tests pass (pre-existing issues MUST be fixed) - [ ] Linting clean - [ ] Generate has run - [ ] Security scans clean - [ ] Docs updated Commit format: ``` type(scope): description [XXX-XXXX] Body explaining what and why. ``` **Never skip hooks. Never use --no-verify.** ## Phase 5: Session Hand-off Update implementation plan with session summary according to the plan session handoff section. --- ## Quick Reference | Action | Command | | ----------------- | ----------------------------- | | Unit tests | `./gradlew test` | | Integration tests s| `INTEG_TESTS=1 ./gradlew test` | | Smoke tests | `./gradlew verifyPlugin` | | Format & lint | `./gradlew ktlintCheck spotlessApply` |
GitHub에서 보기