revise

Propagate GitHub issue updates across requirements, design, and task stages.

3|Updated Nov 5, 2023
Ready to run
npx skills add https://github.com/Junroot/Nomat --skill revise-junroot
πŸ’¬ Prompt for ChatGPT / Claude Chatβ–Ό
Please help me install this Agent Skill.
Skill: revise
Source: https://github.com/Junroot/Nomat/tree/main/.claude/skills/revise
Command: npx skills add https://github.com/Junroot/Nomat --skill revise-junroot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

μ›Œν¬ν”Œλ‘œμš° 각 λ‹¨κ³„μ˜ 이슈λ₯Ό μˆ˜μ •ν•˜κ³ , 변경이 ν•˜μœ„ 단계 μ΄μŠˆμ— 영ν–₯을 μ£Όλ©΄ μ—°μ‡„μ μœΌλ‘œ ν•¨κ»˜ μˆ˜μ •ν•˜λŠ” μŠ€ν‚¬μ΄λ‹€. ν•œ 이슈의 μˆ˜μ •μ΄ ν•˜μœ„/연쇄 μ΄μŠˆμ— λ―ΈμΉ˜λŠ” 영ν–₯κ³Ό 관계λ₯Ό νŒŒμ•…ν•˜κ³  μΌκ΄€λœ λ³€κ²½ 흐름을 μœ μ§€ν•œλ‹€. 변경이 μ„€κ³„λ‚˜ κ΅¬ν˜„ κ³„νšμ— 영ν–₯을 μ£ΌλŠ” 경우λ₯Ό μžλ™μœΌλ‘œ κ°μ§€ν•˜κ³  ν•„μš”ν•œ μˆ˜μ • 포트λ₯Ό μ œκ³΅ν•œλ‹€.

Core Features & Use Cases

  • μš”κ΅¬μ‚¬ν•­ μˆ˜μ • β†’ 섀계 μ½”λ©˜νŠΈ 및 νƒœμŠ€ν¬μ— 영ν–₯ μ—¬λΆ€λ₯Ό λΆ„μ„ν•˜κ³  μžλ™μœΌλ‘œ 연쇄 μ—…λ°μ΄νŠΈλ₯Ό μ œμ•ˆ
  • 섀계 μˆ˜μ • μ‹œ νƒœμŠ€ν¬ ν•˜μœ„ μ΄μŠˆμ— λŒ€ν•œ μ—…λ°μ΄νŠΈλ₯Ό νŠΈλ¦¬κ±°ν•˜κ³  λ³€κ²½ 내역을 좔적
  • μƒμœ„ μ΄μŠˆμ™€ ν•˜μœ„ 이슈 κ°„μ˜ 관계λ₯Ό μ‹œκ°μ μœΌλ‘œ νŒŒμ•…ν•˜κ³  λ³€κ²½ 이λ ₯ 관리

Quick Start

μ§€μ‹œλœ 이슈 번호λ₯Ό μž…λ ₯ν•˜λ©΄ ν•΄λ‹Ή 이슈λ₯Ό μˆ˜μ •ν•˜κ³  연쇄 μ—…λ°μ΄νŠΈ 흐름을 μ‹œμž‘ν•œλ‹€.

Frequently Asked Questions about revise

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

FAQPage Schema
How do I automate cross-stage GitHub issue updates for requirements and design changes?β–Ό

Automate cross-stage GitHub issue updates by identifying the impact scope of requirement or design changes and applying top-down edits with verification steps to automatically propagate updates to downstream task issues.

How does cascading issue update propagation work when modifying a requirement?β–Ό

Cascading issue update propagation works by analyzing whether a modified requirement issue affects design comments or tasks, then automatically proposing and triggering sequential updates to maintain a consistent change flow across linked issues.

Can I track the impact scope of design changes on downstream task issues in GitHub?β–Ό

Yes, you can track the impact scope of design changes on downstream task issues by triggering updates to sub-issues and visually managing the change history between parent and child issues.

What is the best way to maintain consistent change flow across linked requirements, design, and task issues?β–Ό

Maintain consistent change flow by automatically detecting when modifications impact design or implementation plans, presenting a change plan, and applying verified top-down edits across the issue hierarchy.

Do I need to manually identify which task issues require updates when a design issue changes?β–Ό

No, you do not need to manually identify affected task issues; the workflow automatically detects when design or implementation plans are impacted and provides necessary modification proposals for downstream issues.

Why do my downstream task issues become inconsistent after updating a parent requirement issue?β–Ό

Downstream task issues become inconsistent without automatic propagation, but applying top-down edits with verification steps ensures requirement or design changes cascade correctly to maintain issue hierarchy consistency.