skills.rest
choi-jaehyun
choi-jaehyunCOMMUNITY
Explore all skills by this author →
GitHub

workflow

Coordinate multi-file repository changes with saved plans and structured verification passes.

Updated Feb 21, 2026
Search Tags:#git#workflow#documentation#verification#plan#code-review#session-memory
One-click install
npx skills add https://github.com/choi-jaehyun/jaehyun-claude-workflow --skill workflow-choi-jaehyun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/choi-jaehyun/jaehyun-claude-workflow/tree/main/.agents/skills/workflow
Command: npx skills add https://github.com/choi-jaehyun/jaehyun-claude-workflow --skill workflow-choi-jaehyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate substantial repository work by planning, executing, and verifying multi-file changes.

Core Features & Use Cases

  • Saved plans in quality_reports/plans for traceability.
  • Structured verification passes using dedicated skills like verifier, proofreader, r-reviewer, and domain-reviewer.
  • Session-memory updates documented in AGENTS.md and end-of-session logging in quality_reports/session_logs.

Quick Start

Save a compact plan under quality_reports/plans/YYYY-MM-DD_short-description.md, then implement changes and verify with the relevant local skills.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I coordinate multi-file repository changes with a structured plan?▼

Coordinating multi-file repository changes requires saving a compact plan under quality_reports/plans, executing the updates, and running structured verification passes. This enforces traceability and session-memory updates across long-running workflows.

What is the best way to verify code changes across multiple files?▼

Verifying code changes across multiple files is best handled by running structured verification passes using dedicated skills like verifier, proofreader, r-reviewer, and domain-reviewer. This ensures comprehensive quality checks after implementation.

Do I need to read git logs and AGENTS.md before starting a long-running workflow?▼

Yes, reading git logs and AGENTS.md before starting a long-running workflow is required. Reading these files provides the necessary context for planning and executing substantial multi-file repository work effectively.

How do I maintain session-memory updates for long-running workflows?▼

Maintaining session-memory updates for long-running workflows is done by documenting changes in AGENTS.md and logging the end of the session in quality_reports/session_logs. This ensures continuity and traceability for future work.

When should I not use a plan-build-verify loop for repository work?▼

A plan-build-verify loop for repository work should not be used for simple, single-file edits that do not require saved plans or structured verification. It is specifically designed for substantial repository work needing traceability and multi-file coordination.

Related Skills

Explore More Software Engineering Skills→
hikchhikch

checkpointing

Parse CLI logs and update agent configuration files with session checkpoints.

Community
Advanced
zereightzereight

zereight-review

Coordinate subagent-based code-review passes and synthesize CodeRabbit-style PR feedback.

Community
Advanced
MrPointerMrPointer
2

developing-plan-reviewers

Create domain-specialized AI reviewer agents for project planning workflows.

Community
Advanced
jaqgjaqg

git-sync

Group modified and untracked files into logical git commits and print the command sequence.

Community
Intermediate