aps-landing
Ensures atomic, crash-safe operations for merging work in the APS loop.
Install
mkdir -p .claude/skills/aps-landing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16562" && unzip -o skill.zip -d .claude/skills/aps-landing && rm skill.zipInstalls to .claude/skills/aps-landing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Crash-safe merge boundary and race-free reconciliation for the APS loop. Makes the LAND checkpoint a fenced sequence (LANDING token, merge, MERGED record, set Merged, then cleanup) that resumes without duplicate merges, and makes parallel waves race-free via a single-writer status queue and actual-file wave locks. Use when landing work or coordinating parallel execution: "land this item", "merge and reconcile the plan", "run a parallel wave", "resume an interrupted merge", "did the merge land", "set the item to Merged", "reconcile status updates from workers".Key capabilities
- →Manage crash-safe merge boundaries for the APS loop
- →Ensure race-free reconciliation for parallel waves
- →Record merge SHAs in journal and work item status
- →Disambiguate resume after crashes in the split-brain window
- →Implement single-writer reconciliation for parallel waves
- →Enforce wave file-locks based on actual changed files
How it works
This skill implements a fenced landing sequence for merges, recording `LANDING` and `MERGED` tokens in the journal and work item status. It uses an append-only queue for worker status updates and a single conductor for serial reconciliation, along with file-locks based on actual changed files for parallel waves.
Inputs & outputs
When to use aps-landing
- →Landing work items in the APS loop
- →Resuming interrupted merges
- →Coordinating parallel execution waves
About aps-landing
Implements a fenced landing sequence to ensure that git merges, status updates, and journal records remain consistent during crashes. It uses file locks and status queues to handle parallel reconciliation.
>-
When not to use it
- →When the task is not related to landing work items in the APS loop
- →When reordering or skipping journal writes in the landing sequence
- →When a worker subagent directly writes index/module files
Limitations
- →Does not allow reordering or skipping journal writes in the landing sequence
- →Does not allow worker subagents to directly write index/module files
- →Does not self-declare `Complete` status for merged items
How it compares
This skill provides crash-safe merge boundaries and race-free reconciliation for parallel execution, preventing duplicate merges and lost status updates, unlike a manual process that could lead to data corruption or inconsistencies.
Compared to similar skills
aps-landing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| aps-landing (this skill) | 0 | 1mo | No flags | Advanced |
| github-project-management | 4 | 6mo | Review | Advanced |
| conductor-setup | 3 | 4mo | Review | Beginner |
| issue-manage | 2 | 5mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
github-project-management
ruvnet
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
conductor-setup
sickn33
Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)
issue-manage
catlog22
Interactive issue management with menu-driven CRUD operations. Use when managing issues, viewing issue status, editing issue fields, performing bulk operations, or viewing issue history. Triggers on "manage issue", "list issues", "edit issue", "delete issue", "bulk update", "issue dashboard", "issue history", "completed issues".
gsd-executor
toonight
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management
init-harness
mylukin
Creates AI agent task management structure with feature backlog (ai/tasks/), TDD enforcement, and progress tracking. Use when setting up agent-foreman, initializing feature-driven development, creating task backlog, or enabling TDD mode. Triggers on 'init harness', 'setup feature tracking', 'create feature backlog', 'enable strict TDD', 'initialize agent-foreman'.
team-coordination
alinaqi
Multi-person projects - shared state, todo claiming, handoffs