kaizen-sections

Name: kaizen-sections
Availability: InStock
Author: Garsson

Organize PRs and issues into named sections with marker attachments.

Updated Mar 16, 2026

Search Tags:#cli #structure #issues #pr #attachments #sections #marker-comments

Ready to run

npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-sections

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kaizen-sections
Source: https://github.com/Garsson-io/kaizen/tree/main/.agents/skills/kaizen-sections
Command: npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-sections

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured PRs and Issues enable teams to read, organize, and attach targeted content without rewriting entire bodies.

Core Features & Use Cases

High-Level API for domain workflows (reviews, plans, metadata) and Low-Level API for raw section/attachment CRUD.
Use cases include organizing PR bodies, adding marker comments to issues, and storing structured findings and plans.

Quick Start

Use the high-level API to read or write a named section in PRs and issues and manage marker attachments on issues.

Frequently Asked Questions about kaizen-sections

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

FAQPage Schema

How do I structure pull requests with named sections to improve readability?▼

Use a high-level API to organize pull requests into named sections, enabling targeted content updates without rewriting the entire body. This improves readability and traceability during code reviews and repository maintenance.

What are marker attachments in GitHub issues and how do they work?▼

Marker attachments in GitHub issues are structured data points managed through low-level CRUD editors. They allow you to store structured findings and plans directly on issues, improving traceability and organization for issue tracking workflows.

Can I add structured metadata to PR bodies without rewriting the entire description?▼

Yes, you can add structured metadata to PR bodies without rewriting the entire description by using the high-level API to manage named sections. This allows targeted content updates for reviews, plans, and metadata without altering the full PR body.

Does this section and attachment CRUD approach require any external dependencies?▼

No, this section and attachment CRUD approach requires no external dependencies. It operates independently with a YAML frontmatter-driven entry point, using high-level APIs and low-level editors to manage structured content in PRs and issues.

What is the best way to organize code review findings into traceable issue comments?▼

The best way to organize code review findings into traceable issue comments is to use a high-level API that creates named sections and marker attachments. This stores structured findings directly on issues for improved planning and tracking.