← all publishers

adampie

@adampie source repo

Report this profile Claim this profile

• 5 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Sync · adampie

   Rebase a stack onto a moved trunk, absorb merged layers, and make changes to a lower layer mid-stack, using gh stack sync and gh stack rebase. Use when the user says sync my stack, rebase the stack, main moved, my PR merged, update the stack, or when a change belongs in a branch below the one they are on. Handles rebase conflicts. Does not create pull requests, which stack:submit does.
   0
   installs
2. ▌
   Commit · adampie

   Split a working tree into an ordered stack of branches, each with its own commits, using the gh-stack GitHub CLI extension. Use when the user wants uncommitted work turned into stacked PRs and says things like commit this as a stack, split this into layers, break this up for review, stack these changes, or start a stack. Also adds a layer on top of an existing stack. Does not push or open pull requests, which stack:submit does.
   0
   installs
3. ▌
   Submit · adampie

   Push a stack of branches and create or update their pull requests on GitHub, using gh stack submit. Use when the user says submit the stack, open the PRs, raise these for review, push this up, put these up as PRs, or mark them ready. Opens one draft pull request per layer, each based on the layer below. Does not commit, which stack:commit does, and never merges.
   0
   installs
4. ▌
   Upskill · adampie bundle

   Creates, validates, and reviews Agent Skills inside a marketplace repository. Scaffolds the plugin and SKILL.md, registers the plugin in marketplace.json, and checks the result against the Agent Skills specification. Use when the user asks to create a skill, write a new skill, add a skill to the marketplace, scaffold a plugin, or review, improve, or fix an existing SKILL.md.
   0
   installs
5. ▌
   Fact Check · adampie bundle

   Fact-checks factual claims against live web sources and against the local codebase, reporting each one with a verdict, a correction and a citation. Use when the user asks to fact-check or verify a document, article, draft, README or design doc, to check whether a claim is true, to confirm that what the docs say about the code is still what the code does, to trace whether a stated behaviour holds by following the call paths, to source or back up statements, or to audit the accuracy of what Claude itself said earlier in the conversation. Not a code review: it checks claims made about the code, not the quality of the code.
   0
   installs