implement

Automate issue-to-pull-request workflows with isolated worktrees and tests.

3|Updated Nov 5, 2023
One-click install
npx skills add https://github.com/Junroot/Nomat --skill implement-junroot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/Junroot/Nomat/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/Junroot/Nomat --skill implement-junroot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 스킬은 계획된 task 이슈를 읽고, git worktree를 이용해 격리된 환경에서 구현한 뒤 PR을 생성하는 프로세스를 자동화합니다. 이로써 이슈의 구현 내용과 변경 대상 파일을 바탕으로 코드를 작성하고, 테스트 코드까지 함께 작성하도록 돕습니다.

Core Features & Use Cases

  • 이슈에서 구현 내용과 변경 대상 파일을 파악하고 필요한 선행 작업 여부를 확인합니다.
  • 현재 브랜치를 기준으로 worktree를 생성하고 이슈 번호와 요약으로 브랜치를 구성합니다.
  • 백엔드 및 프런트엔드 아키텍처에 맞춘 구현 흐름과 테스트를 포함한 PR을 생성합니다.
  • 완료 후 CI에 적합한 PR 문서와 테스트 계획을 자동으로 포함합니다.

Quick Start

이슈 번호를 지정하면 해당 이슈를 읽고 격리된 환경에서 구현한 뒤 PR을 생성합니다.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate turning a GitHub issue into a pull request with code and tests?

You can automate issue-to-PR workflows by reading the task issue, creating an isolated git worktree, implementing specified changes with tests, and opening a CI-ready pull request.

What is a git worktree and why use it for issue-driven development?

A git worktree creates an isolated working directory linked to your repository, allowing you to implement issue-specific code changes without affecting your main branch or current working state.

How do I create a pull request that automatically includes a CI-ready test plan?

To create a CI-ready PR, you generate the pull request documentation after implementing changes and writing tests, ensuring the test plan and architecture details are automatically included in the PR description.

Can I enforce Korean commit messages in an automated issue implementation workflow?

Yes, you can enforce Korean commit messages within an automated implementation workflow by configuring the process to generate branch names and commits using the issue summary and Korean formatting rules.

Do I need to manually select files before automating code implementation from an issue?

No, you do not need to manually select files; the automation reads the task issue to identify the implementation content and target files, then verifies any necessary prerequisite tasks before coding.