원클릭으로 Manus에서 모든 스킬 실행

branch-doc-sync

스타0

포크0

업데이트2026년 2월 15일 08:20

Analyze current branch changes against a base branch, identify documentation that should be updated, and directly edit those docs. Use when asked to sync docs with branch changes before merge, release, or PR review.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

honki12345

honki12345/my-agent-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Branch Doc Sync

Goal

Keep documentation aligned with implementation changes in the current working branch.

Skill Resources

Mapping template: assets/config/docs-impact-map.yml
Local impact analyzer: scripts/generate_doc_impact_report.py
Impact summary format: references/report-format.md

Inputs

Base branch (default: origin/main; fallback: main)
Scope (all changed files or selected paths)
Documentation targets (README, docs/**, module docs, runbooks)
Language and style requirements

Workflow

Collect branch deltas.

Run git diff --name-status <base>...HEAD to capture changed files.
Group changes by feature area (API, frontend, config, CI/CD, tests, deployment).

Map code changes to doc targets.

Prefer explicit mapping file when present (for example .github/docs-impact-map.yml).
If mapping is absent, derive by path heuristics and ownership.

Decide update actions.

update: existing doc section is stale.
add: missing section is required by new behavior.
no-change: change is internal and docs remain valid.

Generate an impact summary.

Use scripts/generate_doc_impact_report.py when a quick deterministic report is needed.
Follow references/report-format.md for final summary structure.

Edit docs directly.

Update affected docs in place with concrete behavior/config/command changes.
Keep headings stable and preserve existing document style.
Add short evidence notes (Sources) where appropriate.

Validate doc quality.

Verify commands, env vars, file paths, and links.
Ensure no claims contradict code/config.
Summarize what was changed and why.

Guardrails

Do not edit product code unless explicitly requested.
Do not invent undocumented behavior.
Prefer minimal, targeted edits over broad rewrites.
If evidence is insufficient, mark TODO/assumption explicitly.

References

Use references/report-format.md for impact summary/checklist format.

이 저장소의 다른 Skills

같은 저장소

pr-merge-conflict

honki12345/my-agent-skills

GitHub PR URL을 인자로 받아 merge conflict(병합 충돌) 유무를 판정하고, 충돌이 없으면 즉시 종료한다. 충돌이 있으면 충돌 파일/원인 커밋을 추적해 어떤 PR/브랜치에서 유입된 변경인지 식별한 뒤, 양쪽 PR/이슈의 plans(또는 docs/plan) 문서를 찾아 의도한 구현을 모두 보존하는 형태로 충돌을 해결하고 commit+push 해서 PR이 다시 mergeable 해질 때까지 확인한다. PR 병합 충돌 해결을 요청받으면 사용한다.

2026-02-250

pr-ci-loop

honki12345/my-agent-skills

GitHub PR URL을 인자로 받아 현재 브랜치가 PR의 head branch와 일치하는지 검증한 뒤, GitHub Actions CI 실패 원인을 분석/수정하고 commit+push 후 CI 성공을 폴링으로 확인하는 복구 루프를 수행한다. CodeRabbit/Copilot 같은 코드리뷰 체크는 제외하고 GitHub Actions run만 대상으로 한다. PR CI 실패 복구를 요청받으면 사용한다.

2026-02-170

ship

honki12345/my-agent-skills

변경사항 커밋/푸시 워크플로우 자동화. 이슈 생성, 브랜치 생성, 원자적 커밋, 검증, push, PR 생성 후 CI 폴링/실패 복구까지 한 번에 진행해 달라는 명시적 요청에서 사용한다.

2026-02-170

debug-loop

honki12345/my-agent-skills

버그 상황과 로그를 받아 재현을 최우선으로 수행하고, git 변경/프로젝트 문서 기반 원인 가설을 반복 검증해 해결한다. 방향 변경이 필요하면 사용자 승인 후 진행한다.

2026-02-150

plan-review

honki12345/my-agent-skills

구현 계획 문서를 6가지 관점으로 순차 리뷰하고, 수동 텍스트 승인 루프로 의견/승인을 받아 즉시 반영한 뒤 반복 루프를 수행한다.

2026-02-150

issue-worktree-plan

honki12345/my-agent-skills

GitHub 이슈 URL을 인자로 받아 이슈 정보를 확인하고 git worktree 기반 작업 브랜치를 생성한 뒤 이슈 계획 문서를 만든다. 이슈 URL 기준으로 브랜치/worktree/계획 문서 초기화를 요청할 때 사용한다.

2026-02-150

name	branch-doc-sync
description	Analyze current branch changes against a base branch, identify documentation that should be updated, and directly edit those docs. Use when asked to sync docs with branch changes before merge, release, or PR review.

Branch Doc Sync

Goal

Keep documentation aligned with implementation changes in the current working branch.

Skill Resources

Mapping template: assets/config/docs-impact-map.yml
Local impact analyzer: scripts/generate_doc_impact_report.py
Impact summary format: references/report-format.md

Inputs

Base branch (default: origin/main; fallback: main)
Scope (all changed files or selected paths)
Documentation targets (README, docs/**, module docs, runbooks)
Language and style requirements

Workflow

Collect branch deltas.

Run git diff --name-status <base>...HEAD to capture changed files.
Group changes by feature area (API, frontend, config, CI/CD, tests, deployment).

Map code changes to doc targets.

Prefer explicit mapping file when present (for example .github/docs-impact-map.yml).
If mapping is absent, derive by path heuristics and ownership.

Decide update actions.

update: existing doc section is stale.
add: missing section is required by new behavior.
no-change: change is internal and docs remain valid.

Generate an impact summary.

Use scripts/generate_doc_impact_report.py when a quick deterministic report is needed.
Follow references/report-format.md for final summary structure.

Edit docs directly.

Update affected docs in place with concrete behavior/config/command changes.
Keep headings stable and preserve existing document style.
Add short evidence notes (Sources) where appropriate.

Validate doc quality.

Verify commands, env vars, file paths, and links.
Ensure no claims contradict code/config.
Summarize what was changed and why.

Guardrails

Do not edit product code unless explicitly requested.
Do not invent undocumented behavior.
Prefer minimal, targeted edits over broad rewrites.
If evidence is insufficient, mark TODO/assumption explicitly.

References

Use references/report-format.md for impact summary/checklist format.