decision-doc-sync
Keep Project Decisions in Sync
Structural changes can leave project documentation incomplete or contradictory. This skill identifies affected documents and keeps durable decisions aligned with the code.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "decision-doc-sync" from https://skillstore.io/skills/c3sc0-v4113-decision-doc-sync.md and its manifest at https://skillstore.io/api/skills/c3sc0-v4113-decision-doc-sync/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «decision-doc-sync». A repository introduced a shared component standard and updated its design tokens.
Ожидаемый результат:
- Update DESIGN.md with the token and component rules.
- Review README.md only if the standard changes repository structure.
- Skip AGENTS.md because the change does not alter agent workflow.
Использование «decision-doc-sync». A team selected a queue-based integration after comparing two alternatives.
Ожидаемый результат:
Create the next numbered ADR with Status, Context, Decision, and Consequences. Link related documentation to the ADR instead of repeating the decision.
Аудит безопасности
БезопасноAll six static findings are false positives. Each detection matches Markdown backticks around document names or a link target in SKILL.md, not Ruby or shell execution. No semantic security finding or prompt injection was found in the scanned files.
Факторы риска
⚙️ Внешние команды (6)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/c3sc0-v4113-decision-doc-sync/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/c3sc0-v4113-decision-doc-sync?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/c3sc0-v4113-decision-doc-sync?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c3sc0-v4113-decision-doc-sync/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/c3sc0-v4113-decision-doc-sync.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
c3sc0-v4113. (2026). decision-doc-sync security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/c3sc0-v4113-decision-doc-sync/audits/1Цитата BibTeX
@techreport{c3sc0-v4113-c3sc0-v4113-decision-doc-sync-2026,
author = {c3sc0-v4113},
title = {decision-doc-sync security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/c3sc0-v4113-decision-doc-sync/audits/1},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "decision-doc-sync security audit report (audit version 1)"
version: "1.0"
type: report
authors:
- name: "c3sc0-v4113"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/c3sc0-v4113-decision-doc-sync/audits/1"
identifiers:
- type: other
value: "skillstore:c3sc0-v4113-decision-doc-sync:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Record an architecture change
Identify affected project documents and update the architecture record without duplicating the same fact across files.
Maintain interface standards
Route visual or UX changes to the correct design documentation and check that guidance matches the implementation.
Document operational decisions
Update workflow guidance or create a numbered ADR when a durable operational decision has meaningful alternatives.
Попробуйте эти промпты
A new structural change was made: [describe change]. Identify the existing project documents that require review and explain why.
The interface standard changed: [describe standard]. Classify the change, identify existing files to update, and list the required edits.
We chose [decision] over [alternatives] because [context]. Determine whether an ADR is warranted and draft its required sections.
Review this structural change and the provided documentation: [change and excerpts]. Find contradictions, assign each fact to one source document, and report skipped files with reasons.
Лучшие практики
- Check document existence before proposing edits.
- Keep each durable fact in one authoritative document.
- Reread edited sections against the current code.
Избегать
- Do not duplicate the same decision across multiple documents.
- Do not rewrite an accepted ADR when a new decision supersedes it.
- Do not create an ADR for a local feature change without durable alternatives.
Часто задаваемые вопросы
What changes activate this skill?
Which documents does it manage?
Does it always create an ADR?
How does it avoid duplicate facts?
Can it rewrite an accepted ADR?
What does the final report include?
Сведения для разработчиков
Автор
c3sc0-v4113Лицензия
Apache-2.0
Версия автора
v1.0
Ревизия Skillstore
r1
Примечание о версии
Заявленная автором версия не соответствует SemVer.
Ссылка
2b27e7a2fcb182c7518cb7fb98bf9e564128332c
Актуальность поддержки
02.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов