CMP-62 chore: add gh-stack skill

[ripgrim]

No description provided.

[github-actions]

Retargeted this onto main.

release is the default branch so that a plain clone runs the last tagged release, but nothing merges into it — it is fast-forwarded onto the tag by the Release workflow and that is all. Changes go to main, and reach release when a release is cut.

Nothing is wrong with your branch. If the diff now shows commits that are already on main, rebase and force-push:

git fetch origin main
git rebase origin/main
git push --force-with-lease

[cubic-dev-ai]

1 issue found across 4 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".agents/skills/gh-stack/references/stack-design.md">

<violation number="1" location=".agents/skills/gh-stack/references/stack-design.md:18">
P3: Missing space before inline code backtick: "means" runs directly into the opening backtick of `` `unstack` ``. The rendered output will read "means`unstack`" rather than "means `unstack`".</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P3: Missing space before inline code backtick: "means" runs directly into the opening backtick of `unstack`. The rendered output will read "meansunstack" rather than "means unstack".

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At .agents/skills/gh-stack/references/stack-design.md, line 18:

<comment>Missing space before inline code backtick: "means" runs directly into the opening backtick of `` `unstack` ``. The rendered output will read "means`unstack`" rather than "means `unstack`".</comment>

<file context>
@@ -0,0 +1,97 @@
+A stack is a dependency chain. If code in one layer depends on code in another, the dependency must
+live in the same branch or a lower one. That constraint is much cheaper to satisfy by planning than
+by restructuring later, because there is no non-interactive in-place reorder — fixing the order
+means`unstack` and `init` again.
+
+Decide the layers first, then write code into them:
</file context>