docs(agents): add internal meta-issue-creation and meta-pr-creation skills - #919
Open
coderdan wants to merge 2 commits into
Open
docs(agents): add internal meta-issue-creation and meta-pr-creation skills#919coderdan wants to merge 2 commits into
coderdan wants to merge 2 commits into
Conversation
…kills Agent-authored issues and PRs on this repo have had no documented structure. These two skills capture the conventions that worked in practice: Background / Problem / Proposal issue sections written for a reader new to CipherStash, signed-commit verification and the rebase recipe for an unsigned commit, the changeset/skills/meta-file checklist by pointer to AGENTS.md, and the reference traps (bare #N autolinks; Linear CIP- numbers never appear on GitHub). They live in .claude/skills/ deliberately: skills/ ships to customers inside the stash tarball via packages/cli/tsup.config.ts, and these are internal-only.
|
coderdan
marked this pull request as draft
August 19, 2026 03:50
coderdan
marked this pull request as ready for review
August 19, 2026 04:04
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.
Summary
Agents working on this repo now file issues and open PRs regularly, with no documented structure — quality has depended on the session. This adds two internal skills setting the conventions: a required issue shape (Background / Problem / Proposal) written for a reader who is new to CipherStash, and the branch/commit/PR authoring rules (signed commits, the changeset checklist, PR body sections).
They live in
.claude/skills/, notskills/— everything underskills/ships to customers inside thestashnpm tarball (packages/cli/tsup.config.tscopies the whole directory), and these are internal-only. Themeta-prefix marks them as repo-process skills, distinct from the customer-facingstash-*set.Changes
.claude/skills/meta-issue-creation/SKILL.md— pre-filing checks (search existing issues open and closed, verify claims against code, pick the right repo), the required section structure, dumbed-down wording rules, cross-linking in both directions..claude/skills/meta-pr-creation/SKILL.md— branch/commit conventions, signed-commit verification (%G?) and the re-sign rebase recipe, the AGENTS.md pre-PR checklist by pointer, PR body structure, force-push etiquette.Both encode two reference traps from recent sessions: bare
#Nautolinks to an unrelated issue unless a GitHub reference is intended, and internal Linear (CIP-) numbers must never appear on GitHub.Verification
Docs-only; no build or tests apply. Checked that
.claude/skills/is outside every tarball copy path (tsup.config.tscopiesskills/anddoctrine/only). No changeset:.claude/is internal and ships nowhere, per the changeset rule these skills themselves document.Related
Conventions distilled from the sessions around #895/#897 (skill corrections), #896 (hazard comments), and #918 (issue filing).