loam-amend-status-quick

Analyze git commits, manifests, plan-docs, and seals to summarize amendment cycle status.

2|Updated May 3, 2026

Search Tags:#git #diagnostics #status #progress #amendment #cycle

Ready to run

npx skills add https://github.com/lukeivers/loam --skill loam-amend-status-quick

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: loam-amend-status-quick
Source: https://github.com/lukeivers/loam/tree/main/plugins/dev-sdlc/skills/loam-amend-status-quick
Command: npx skills add https://github.com/lukeivers/loam --skill loam-amend-status-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rapid diagnostic tool for understanding the current state of an ongoing or paused amendment cycle, helping users identify completed steps, pending actions, and potential issues efficiently.

Core Features & Use Cases

Cycle Status Check: Summarizes commits landed in the amendment ladder, including the plan-doc, source edits, apply, seal, and backfill.
Progress Analysis: Measures which steps have been completed and which remain, facilitating quick resumption or troubleshooting of the cycle.
Use Case: When inheriting a paused build or reviewing a pull request with multiple cycle commits, use this Skill to determine the current position and next action required.

Quick Start

Ask the AI: "Show me the current status of the latest amendment cycle to understand what steps have been completed and what remains."

Frequently Asked Questions about loam-amend-status-quick

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

FAQPage Schema

How do I check the status of a multi-stage amendment cycle using git commits?▼

Amendment cycle progress is measured by analyzing recent git commits alongside manifest files and plan-docs. This identifies which specific stages, such as source edits, apply, seal, and backfill, have been completed and which remain pending within the development cycle.

How do I resume a paused development cycle with multiple git commits?▼

A development cycle gets stuck when git commits, manifest files, or plan-docs show incomplete stages. Diagnosing the cycle involves examining these artifacts to pinpoint missing sidecar seals or pending backfill steps, revealing the specific issue blocking progress.

What is the best way to review a pull request with multiple cycle commits?▼

Reviewing a pull request with multiple cycle commits involves examining recent git logs, manifest files, and plan-docs. This analysis produces a high-level status summary identifying the amendment cycle's current position, completed steps, and pending actions.

Do I need manifest files and plan-docs to assess amendment cycle progress?▼

Yes, manifest files and plan-docs are required to assess amendment cycle progress. Accessing these alongside git logs and sidecar seals is necessary to produce an accurate, high-level status summary identifying pending steps and potential issues.

What issues can occur during a multi-step code update workflow?▼

Issues during a multi-step code update workflow include incomplete stages in the amendment ladder, such as missing source edits, apply, seal, or backfill steps. Analyzing git commits and manifest files identifies these pending actions and potential cycle issues.