Conversation
- Add 12 undocumented packages to main README catalog (sc-ai-cli, sc-ci-automation, sc-codex, sc-coding-agent-hardening, sc-commit-push-pr, sc-just, sc-kanban, sc-launch-term, sc-launchpad, sc-roslyn-diff, sc-rust, sc-startup) - Write sc-docling-pdf README.md (was genuinely missing) - Update Find the Right Package table with all 18 packages - Update Package Overview table with all 13 new entries - Follow existing badge/tier/doc-link format consistently
docs: add missing README catalog entries for 13 packages + sc-docling-pdf README
docs: establish canonical ATM naming conventions
feat: add Fable, Codex model, and cmux launch targets
main->develop
main->develop
randlee
marked this pull request as ready for review
August 30, 2026 19:45
Rebase onto feature/sc-git-worktree-gh-stack resolved generated registry files to the lower layer's state; regenerated from manifests so all entries match (platform packages 0.13.0, sc-refactory 0.2.0). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Rebasing refactory off the abandoned feature/sc-gh-stack and feature/sc-git-worktree-gh-stack stack dropped an unrelated version bump that sc-git-worktree had picked up from that stack, desyncing it from the marketplace-wide 0.13.0 bump and the nuget registry. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
randlee
removed this pull request from stack #108
September 23, 2026 04:36
…ack-view (0.1.0) Fresh package replacing the managing-gh-stacks attempt (PR #101). Two skills: - sc-gh-stack: progressive-disclosure table of contents over references/ for the append-only stack model, lifecycle workflow, preconditions distilled from five production phases (link --base, frozen layers, one stack writer, QA/CI on the top, trunk freeze, no red-bottom-alone merges, full branches[] before scoped merges), and recipes for cut-layer, link, restack (insert, remove red layer, collapse bottom), land (atomic merge, merge-async and non-linear fallbacks) and stale per-worktree tracking; the gh stack v0.1.0 command guide, troubleshooting signatures and stack-design guidance carried over from the retired generic gh-stack skill; a phase-model worked example. - sc-gh-stack-view: atm-core's gh_stack_view.py ported (default view now shows every open stack on any trunk) with its regression tests. Scripts are stdlib-only and read-only: gh_stack_view.py, gh_stack_chain_check.py (pre-link linear-ancestry / PR-base / clean-merge check that prints the exact link command), gh_stack_shared.py (timeouts, actionable hints, never-a-traceback guard). 46 unit tests; registries regenerated at 0.1.0. Also: pytest.ini collects the package tests; requirements-dev.txt gains pypdf so the docling suite collects; ai-cli hook test fixtures call python3. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Blocking: chain check printed PR numbers as `#N` (a shell comment), now bare
numbers and no `next:` line unless LINKABLE; develop-stack recipe left PRs
unrebased (non-linear, unlandable), now chains with one merge-forward per
layer and runs the chain check; three inconsistent `link` rules unified
(full `--base` list is canonical, `link <stack#> <pr#>` appends only);
"out-of-date with base" remedy no longer suggests `gh stack sync`.
Should-fix: red layer is removed, never "landed as a pair"; fix tasks on
frozen layers route to a new top layer; land by stack number; insert requires
containment + chain check; collapse resets the rebased child; `--no-track`
on worktree add; `{owner}/{repo}` in gh api paths; stack-number recovery via
`gh stack checkout <pr#>`; view skill gets the full installation doc and
`$CLAUDE_PLUGIN_ROOT` script paths.
Scripts: skipped (unreadable) worktrees now exit 1 with LANDING unjudged;
unresolved PRs render as unknown instead of stale; fetch timeouts degrade to
unknown; behind-a-moved-trunk gets its own icon and downgrades needsRebase to
a note; pool capped at 4; actionable hints for rate-limit/auth/network; real
temporary-repo tests for merge-tree/is-ancestor and a shell round-trip test
for the link command (55 tests).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
feat(sc-gh-stack): stacked-PR skill from field lessons + sc-gh-stack-view (0.1.0)
# Conflicts: # .claude-plugin/marketplace.json # .claude-plugin/registry.json # docs/registries/nuget/registry.json
The nuget/.claude-plugin registries were stale post-merge (sc-ci-automation still showed 0.12.0 despite its manifest being at 0.13.0, and sc-gh-stack was missing after landing via PR #109). Regenerated from current manifests with no manifest version changes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
New `sc-worktree-create-stacked` agent and `--create-stacked <layer> <parent> <trunk> [--above <layer>]`: cut a gh-stack layer from the parent's PUSHED head with --no-track, refuse bad cuts before any mutation (layer exists, parent not pushed / landed / off trunk, insert target not stacked on the parent), record parent_sha in tracking, and return a stack_handoff block (push, PR base, link or mid-stack insert sequence, writer rules) for the agent that works in the worktree. The plain create agent is untouched; the skill and command route stack layers to the new agent. Cleanup/abort refuse to delete a branch that live layers were cut from unless git shows a merge commit landing (STACK.HAS_CHILDREN, batch `stack_blocked`). Scan reports stack_parent_advanced / stack_parent_landed on layer rows. Fixes: remote-ref bases no longer become the new branch's upstream (--no-track); merge detection recognises the `+` marker for branches checked out in other worktrees. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…handoff and guards - stack_handoff split by role: `writer` (WIP commit first, push -u, one rebase rule, no gh stack write commands) and `stack_writer` (PR with base = parent, gh stack checkout in the new worktree, link on top, or the insert sequence with merge-forward by EVERY layer above) - STACK.PARENT_HAS_CHILD: refuse an append onto a parent that already has a live layer - find_stack_children checks liveness against git/filesystem and treats the layer an inserted layer sits under (`stack.above`) as its child; is_landed_by_merge fails closed when its first-parent window is exhausted - cleanup judges landing against origin/<children's trunk>, only when children exist; batch cleanup never sweeps a fresh layer with no commits; actionable reconcile hints - scan: parent_advanced now means "layer does not contain origin/<parent>" (clears after the writer's rebase or a merge-forward); landed recommendation adds the diff-before-reset rule - shell-safe handoff commands (quoted heredoc PR body, quoted paths) - docs aligned (agent, reference, skill, command, changelog); sc-gh-stack recipe-cut-layer points at --create-stacked (sc-gh-stack 0.1.1) - tests: 42 real-git stack tests; package tests added to local pytest testpaths Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
feat(sc-git-worktree): stack-aware worktree creation (0.14.0)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack created with GitHub Stacks CLI • Give Feedback 💬