require-update

Name: require-update
Availability: InStock
Author: Harries

Update specified sections of requirements documents while preserving the rest.

1|Updated Dec 22, 2025

Search Tags:#git #documentation #requirements #incremental-update #revision-history #section-mapping

Ready to run

npx skills add https://github.com/Harries/hydpromptkit --skill require-update

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: require-update
Source: https://github.com/Harries/hydpromptkit/tree/main/skills/require-update
Command: npx skills add https://github.com/Harries/hydpromptkit --skill require-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

实现对现有需求文档的增量更新，在保持文档结构不变的前提下，按指定章节或智能匹配更新内容，并确保变更可追溯。

Core Features & Use Cases

支持按 -f 指定的文档进行增量更新，指定 -s 或通过智能匹配选择章节
自动生成并维护修订历史，确保文档变更可审计
提交修改到 Git 仓库，确保变更可回溯与团队协作

Quick Start

使用该技能在需要更新需求文档时执行增量更新操作，传入要修改的文档路径及可选章节。

Frequently Asked Questions about require-update

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

FAQPage Schema

How do I update specific sections of a requirements document while preserving the rest?▼

Updating specific sections of a requirements document while preserving the rest is done through incremental updates, targeting sections like overview or function via specified flags or smart matching.

How does Git integration work for requirements document revision history?▼

Git integration for requirements revision history works by automatically creating backups, generating changelists, and committing incremental modifications to the repository, ensuring all document changes remain traceable and auditable for team collaboration.

Can I use smart matching to update requirement sections when the section name is not provided?▼

Yes, you can use smart matching to update requirement sections when the section name is not provided, allowing the system to automatically identify and apply updates to the correct parts of the document.

What is the best way to ensure traceability when modifying functional and nonfunctional requirements?▼

The best way to ensure traceability when modifying functional and nonfunctional requirements is to automate changelist creation, maintain revision history, and commit changes to a Git repository during the document update process.

Do I need existing documentation files to use incremental update operations?▼

Yes, you need existing documentation files to use incremental update operations, as the process applies modifications to a specified existing requirements document rather than creating one from scratch.