revise

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

3|Updated Nov 5, 2023
One-click install
npx skills add https://github.com/Junroot/Nomat --skill revise-junroot
Or copy as Structured Prompt for Agent
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.