[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79R1SHFXRXWN9BJBCE2J530":3,"skill-same:01M79R1SHFXRXWN9BJBCE2J530":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M79R1SHFXRXWN9BJBCE2J530","migrate-check",null,"Pre-flight safety check for Prisma\u002FSQL migrations. MUST be run before creating or applying any migration in a project whose database is shared Postgres. Opens with a written GO or NO-GO verdict, then classifies every SQL statement additive vs destructive, checks migration-history drift and folder reuse, enforces create-only plus deploy discipline, and identifies the backup path first. Never fixes anything - it blocks and explains.","AaravChadha\u002Facstack","AaravChadha","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224610398?v=4","01M79QZCAGEMRNH32DKH6VC5RJ","01M79QZCB37TR94RNR32TM7YTV",2,"MIT","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-check\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: migrate-check\ndescription: \"Pre-flight safety check for Prisma\u002FSQL migrations. MUST be run before creating or applying any migration in a project whose database is shared Postgres. Opens with a written GO or NO-GO verdict, then classifies every SQL statement additive vs destructive, checks migration-history drift and folder reuse, enforces create-only plus deploy discipline, and identifies the backup path first. Never fixes anything - it blocks and explains.\"\nargument-hint: \"[prisma\u002Fmigrations\u002F\u003Cfolder>]\"\nallowed-tools: Read, Grep, Glob, Bash(git diff:*), Bash(git log:*), Bash(git status:*), Bash(ls:*), Bash(cat:*), Bash(npx prisma migrate status:*)\n---\n\n# \u002Fmigrate-check — the gate before the shared database\n\nA teammate's migration once dropped a table from a shared production\ndatabase. This skill exists so that never happens again. It is structurally\nread-only: the tool whitelist has no Edit, no Write, and no prisma\nsubcommand that mutates anything. It blocks and explains; it never fixes.\n(One residual: `git log` and `git diff` accept `--output=FILE`, which a\nprefix grant can't exclude; the skill never uses it — see check.sh §13.)\n\n`Adjacent skills:` \u002Fsecure (security review; \u002Fmigrate-check is DB-change\nsafety) · \u002Faudit code (defects in code; this gates schema changes).\n\n\u003C!-- acstack:runtime -->\nRun before the skill's steps — per invocation, not per session (4.36); failures degrade to markdown:\n```bash\nlink=\"$(readlink \"$HOME\u002F.claude\u002Fskills\u002Fhealth\" 2>\u002Fdev\u002Fnull || true)\"   # empty = not symlinked\npack=\"$(dirname \"$(dirname \"$link\")\")\"   # NEVER trust this unless $link was non-empty\nif [ \"${link#\u002F}\" != \"$link\" ] && [ -x \"$pack\u002Fbin\u002Facstack-config\" ] && ! \"$pack\u002Fbin\u002Facstack-config\" runtime | grep -q '=off'; then\n  \"$pack\u002Fbin\u002Facstack-config\" || true          # resolved keys, with sources\n  \"$pack\u002Fbin\u002Facstack-update-check\" || true    # ≤1 fetch\u002Fday; silent ONLY if already checked today\n  \"$pack\u002Fbin\u002Facstack-recall\" || true          # LEARNINGS.md + bug-class names, capped 3KB\nelse\n  echo \"runtime off — proceeding without recall\u002Fupdate-check\"\nfi\n```\n\u003C!-- \u002Facstack:runtime -->\n\n\u003C!-- acstack:principles -->\n## Operating principles\n\n- Be direct. Push back in writing when the plan or the user is wrong. No sycophancy.\n- Never delete a decision. Supersede it: `~~old~~ → **Verdict (YYYY-MM-DD):** new call — reason.`\n- Never fix, tune, or delete a test or eval case to raise a score. Log the miss honestly and leave the case unchanged.\n- Name exact things: regex patterns, function signatures, model names, before → after numbers. Never \"fixed bugs\".\n- Attribution: follow the project's `attribution` setting (default `none`) — no AI-tool mentions in generated docs, no attribution trailers in commits or PRs. Commit with explicit `-m`\u002F`-F` messages only.\n- Config: read `.claude\u002Facstack.md` at the project root (fall back to `~\u002F.claude\u002Facstack.md`) before acting. `## Settings` keys override pack defaults; a `## \u003Cskill-name>` section overrides both. Unknown keys and sections are ignored.\n- Docs: BRIEF.md (frozen seed) \u002F PLAN.md (living plan) \u002F JOURNAL.md (rolling journal). If the repo uses legacy names (PLANNING_PROMPT.md \u002F PLANNING.md \u002F STATUS.md), use those instead — never create both.\n- Recall: if `LEARNINGS.md` exists at the project root, read it before starting.\n- Conduct: follow the `acstack-conduct` block in this repo's AGENTS.md — the word is the mode; the user sets the pace.\n- Hackathon lane: if the project's AGENTS.md carries the `acstack:hackathon-lane` block, only `\u002Fdo` changes the repository during the event. Any other skill that would write a tracked file, commit or push says what it would have done and stops; a change that is not a task goes through the lane's operator route.\n\u003C!-- \u002Facstack:principles -->\n\n## Procedure\n\n1. **Resolve the safety level** from config `db:`. Default when unspecified\n   is **shared-prod** — the conservative assumption. `local` → lighter path\n   (step 8). `none` → say so in one line and stop.\n\n   **No-database autodetect.** When `db:` is *unset* AND the project shows\n   **no** database signal at all — no `prisma\u002F`, no `migrations\u002F`\n   directory, no `*.sql`, no `alembic.ini`\u002F`Gemfile`, no ORM or driver\n   dependency in a manifest, no `DATABASE_URL` in `.env`\u002F`.env.example` —\n   open with *\"no database in this project — nothing to pre-flight\"* and\n   stop there. That is the honest answer up front, rather than reaching it\n   the long way through a failed stack lookup in step 2. **The conservative\n   default is unchanged whenever a database MIGHT exist:** any one signal\n   present, or `db:` set explicitly, means shared-prod strictness as\n   before. Absence of every signal is the only trigger — never a partial\n   match, and never an inference from \"I couldn't find the stack.\"\n2. **Identify the target**: the folder or file named in the arguments,\n   else the newest unapplied migration. Resolution is stack-dependent —\n   `npx prisma migrate status` for Prisma; otherwise the newest unapplied\n   file in the project's migrations directory (Drizzle, Rails, Alembic,\n   Flyway, plain SQL). **If the stack cannot be determined or the target\n   cannot be resolved, say exactly that and ask for the target path —\n   never assume Prisma.**\n\n   **Honest scope on non-Prisma stacks.** Steps 3 (backup path) and 4\n   (classification) are stack-agnostic and run normally. Steps 5, 6, 7,\n   and 8 name Prisma commands specifically, and the `allowed-tools`\n   whitelist deliberately permits no migration CLI except\n   `prisma migrate status` — running an\n   arbitrary stack's CLI is exactly the mutation risk this skill exists\n   to prevent. So on Drizzle\u002FAlembic\u002FRails\u002FFlyway\u002Fplain SQL, say plainly:\n   *\"history-drift and command-discipline checks skipped — \u003Cstack> CLI is\n   outside this skill's read-only whitelist; verify applied-migration\n   history manually before the GO.\"* A narrowed verdict stated is honest;\n   a full verdict implied from a partial check is not.\n3. **Backup and undo path FIRST.** Name the exact backup command (default\n   `pg_dump \"$DATABASE_URL\" > backups\u002Fpre_\u003Ctimestamp>.sql`; config\n   `## migrate-check` `backup-command` overrides) and the restore step. If\n   no undo path can be identified, the verdict is **NO-GO** — automatically.\n4. **Classify every statement** in the migration SQL per\n   `references\u002Fsql-classification.md`. Output a per-statement table:\n   statement \u002F class \u002F risk \u002F safe alternative where one exists.\n5. **History drift and folder reuse.** Compare `migrate status` output with\n   `prisma\u002Fmigrations\u002F`. Enforce the re-land rule: re-landing a previously\n   dropped migration requires a NEW timestamped folder — a reused folder\n   name already recorded in `_prisma_migrations` is silently skipped and\n   the table never created. Flag any drift between recorded history and the\n   folder set.\n6. **Command discipline** (shared-prod): author with\n   `npx prisma migrate dev --create-only`, apply with\n   `npx prisma migrate deploy`. NEVER plain `migrate dev` and never\n   `db push` against a shared database — both can reset or drift it.\n7. **Sequencing.** Migrations are applied manually BEFORE merging code that\n   depends on them: CI\u002Fhosting builds run `prisma generate && next build`\n   (or equivalent) and never run migrations, so merged code referencing a\n   not-yet-existing column fails at runtime. Confirm the ordering plan.\n8. **`db: local` lighter path**: file backup\n   (`cp prisma\u002Fdev.db prisma\u002Fdev.db.backup_\u003Ctimestamp>`), plain\n   `migrate dev` acceptable, but statement classification (step 4) still\n   runs — destructive is destructive on any database.\n\n## The verdict\n\n**The verdict is the report's FIRST line**, then the evidence that earned\nit — a reader who stops after one line must still get the answer. Restate\nit at the end as a written block, always:\n\n- `**Verdict: GO**` — only when every statement is additive, history is\n  clean, and the backup path is named. Include the exact next commands in\n  order.\n- `**Verdict: NO-GO — \u003Creason>**` — for any destructive statement without\n  an explicit user-acknowledged plan, missing undo path, folder reuse, or\n  history drift. Include: what to check (expected row counts, expected\n  `migrate status` output), and a symptom → cause → action table for the\n  likely failure modes.\n\nDestructive operations are never a hard stop forever — they are a stop\nuntil the user explicitly acknowledges the classification table and the\nbackup is confirmed taken. The skill's job is to make \"I didn't realize it\nwould drop that\" impossible.\n","# \u002Fmigrate-check — the gate before the shared database\n\nA teammate's migration once dropped a table from a shared production\ndatabase. This skill exists so that never happens again. It is structurally\nread-only: the tool whitelist has no Edit, no Write, and no prisma\nsubcommand that mutates anything. It blocks and explains; it never fixes.\n(One residual: `git log` and `git diff` accept `--output=FILE`, which a\nprefix grant can't exclude; the skill never uses it — see check.sh §13.)\n\n`Adjacent skills:` \u002Fsecure (security review; \u002Fmigrate-check is DB-change\nsafety) · \u002Faudit code (defects in code; this gates schema changes).\n\n\u003C!-- acstack:runtime -->\nRun before the skill's steps — per invocation, not per session (4.36); failures degrade to markdown:\n```bash\nlink=\"$(readlink \"$HOME\u002F.claude\u002Fskills\u002Fhealth\" 2>\u002Fdev\u002Fnull || true)\"   # empty = not symlinked\npack=\"$(dirname \"$(dirname \"$link\")\")\"   # NEVER trust this unless $link was non-empty\nif [ \"${link#\u002F}\" != \"$link\" ] && [ -x \"$pack\u002Fbin\u002Facstack-config\" ] && ! \"$pack\u002Fbin\u002Facstack-config\" runtime | grep -q '=off'; then\n  \"$pack\u002Fbin\u002Facstack-config\" || true          # resolved keys, with sources\n  \"$pack\u002Fbin\u002Facstack-update-check\" || true    # ≤1 fetch\u002Fday; silent ONLY if already checked today\n  \"$pack\u002Fbin\u002Facstack-recall\" || true          # LEARNINGS.md + bug-class names, capped 3KB\nelse\n  echo \"runtime off — proceeding without recall\u002Fupdate-check\"\nfi\n```\n\u003C!-- \u002Facstack:runtime -->\n\n\u003C!-- acstack:principles -->\n## Operating principles\n\n- Be direct. Push back in writing when the plan or the user is wrong. No sycophancy.\n- Never delete a decision. Supersede it: `~~old~~ → **Verdict (YYYY-MM-DD):** new call — reason.`\n- Never fix, tune, or delete a test or eval case to raise a score. Log the miss honestly and leave the case unchanged.\n- Name exact things: regex patterns, function signatures, model names, before → after numbers. Never \"fixed bugs\".\n- Attribution: follow the project's `attribution` setting (default `none`) — no AI-tool mentions in generated docs, no attribution trailers in commits or PRs. Commit with explicit `-m`\u002F`-F` messages only.\n- Config: read `.claude\u002Facstack.md` at the project root (fall back to `~\u002F.claude\u002Facstack.md`) before acting. `## Settings` keys override pack defaults; a `## \u003Cskill-name>` section overrides both. Unknown keys and sections are ignored.\n- Docs: BRIEF.md (frozen seed) \u002F PLAN.md (living plan) \u002F JOURNAL.md (rolling journal). If the repo uses legacy names (PLANNING_PROMPT.md \u002F PLANNING.md \u002F STATUS.md), use those instead — never create both.\n- Recall: if `LEARNINGS.md` exists at the project root, read it before starting.\n- Conduct: follow the `acstack-conduct` block in this repo's AGENTS.md — the word is the mode; the user sets the pace.\n- Hackathon lane: if the project's AGENTS.md carries the `acstack:hackathon-lane` block, only `\u002Fdo` changes the repository during the event. Any other skill that would write a tracked file, commit or push says what it would have done and stops; a change that is not a task goes through the lane's operator route.\n\u003C!-- \u002Facstack:principles -->\n\n## Procedure\n\n1. **Resolve the safety level** from config `db:`. Default when unspecified\n   is **shared-prod** — the conservative assumption. `local` → lighter path\n   (step 8). `none` → say so in one line and stop.\n\n   **No-database autodetect.** When `db:` is *unset* AND the project shows\n   **no** database signal at all — no `prisma\u002F`, no `migrations\u002F`\n   directory, no `*.sql`, no `alembic.ini`\u002F`Gemfile`, no ORM or driver\n   dependency in a manifest, no `DATABASE_URL` in `.env`\u002F`.env.example` —\n   open with *\"no database in this project — nothing to pre-flight\"* and\n   stop there. That is the honest answer up front, rather than reaching it\n   the long way through a failed stack lookup in step 2. **The conservative\n   default is unchanged whenever a database MIGHT exist:** any one signal\n   present, or `db:` set explicitly, means shared-prod strictness as\n   before. Absence of every signal is the only trigger — never a partial\n   match, and never an inference from \"I couldn't find the stack.\"\n2. **Identify the target**: the folder or file named in the arguments,\n   else the newest unapplied migration. Resolution is stack-dependent —\n   `npx prisma migrate status` for Prisma; otherwise the newest unapplied\n   file in the project's migrations directory (Drizzle, Rails, Alembic,\n   Flyway, plain SQL). **If the stack cannot be determined or the target\n   cannot be resolved, say exactly that and ask for the target path —\n   never assume Prisma.**\n\n   **Honest scope on non-Prisma stacks.** Steps 3 (backup path) and 4\n   (classification) are stack-agnostic and run normally. Steps 5, 6, 7,\n   and 8 name Prisma commands specifically, and the `allowed-tools`\n   whitelist deliberately permits no migration CLI except\n   `prisma migrate status` — running an\n   arbitrary stack's CLI is exactly the mutation risk this skill exists\n   to prevent. So on Drizzle\u002FAlembic\u002FRails\u002FFlyway\u002Fplain SQL, say plainly:\n   *\"history-drift and command-discipline checks skipped — \u003Cstack> CLI is\n   outside this skill's read-only whitelist; verify applied-migration\n   history manually before the GO.\"* A narrowed verdict stated is honest;\n   a full verdict implied from a partial check is not.\n3. **Backup and undo path FIRST.** Name the exact backup command (default\n   `pg_dump \"$DATABASE_URL\" > backups\u002Fpre_\u003Ctimestamp>.sql`; config\n   `## migrate-check` `backup-command` overrides) and the restore step. If\n   no undo path can be identified, the verdict is **NO-GO** — automatically.\n4. **Classify every statement** in the migration SQL per\n   `references\u002Fsql-classification.md`. Output a per-statement table:\n   statement \u002F class \u002F risk \u002F safe alternative where one exists.\n5. **History drift and folder reuse.** Compare `migrate status` output with\n   `prisma\u002Fmigrations\u002F`. Enforce the re-land rule: re-landing a previously\n   dropped migration requires a NEW timestamped folder — a reused folder\n   name already recorded in `_prisma_migrations` is silently skipped and\n   the table never created. Flag any drift between recorded history and the\n   folder set.\n6. **Command discipline** (shared-prod): author with\n   `npx prisma migrate dev --create-only`, apply with\n   `npx prisma migrate deploy`. NEVER plain `migrate dev` and never\n   `db push` against a shared database — both can reset or drift it.\n7. **Sequencing.** Migrations are applied manually BEFORE merging code that\n   depends on them: CI\u002Fhosting builds run `prisma generate && next build`\n   (or equivalent) and never run migrations, so merged code referencing a\n   not-yet-existing column fails at runtime. Confirm the ordering plan.\n8. **`db: local` lighter path**: file backup\n   (`cp prisma\u002Fdev.db prisma\u002Fdev.db.backup_\u003Ctimestamp>`), plain\n   `migrate dev` acceptable, but statement classification (step 4) still\n   runs — destructive is destructive on any database.\n\n## The verdict\n\n**The verdict is the report's FIRST line**, then the evidence that earned\nit — a reader who stops after one line must still get the answer. Restate\nit at the end as a written block, always:\n\n- `**Verdict: GO**` — only when every statement is additive, history is\n  clean, and the backup path is named. Include the exact next commands in\n  order.\n- `**Verdict: NO-GO — \u003Creason>**` — for any destructive statement without\n  an explicit user-acknowledged plan, missing undo path, folder reuse, or\n  history drift. Include: what to check (expected row counts, expected\n  `migrate status` output), and a symptom → cause → action table for the\n  likely failure modes.\n\nDestructive operations are never a hard stop forever — they are a stop\nuntil the user explicitly acknowledges the classification table and the\nbackup is confirmed taken. The skill's job is to make \"I didn't realize it\nwould drop that\" impossible.\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24},"Read, Grep, Glob, Bash(git diff:*), Bash(git log:*), Bash(git status:*), Bash(ls:*), Bash(cat:*), Bash(npx prisma migrate status:*)","[prisma\u002Fmigrations\u002F\u003Cfolder>]","main","6b5be39937ce3823cf8f58c68aadcfdfda839fa0","skills\u002Fmigrate-check",0,"https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack","https:\u002F\u002Fgithub.com\u002FAaravChadha","2026-09-28 13:07:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add AaravChadha\u002Facstack --skill migrate-check",{"tool":38,"command":39},"bunx","bunx skills add AaravChadha\u002Facstack --skill migrate-check",{"tool":41,"command":42},"pnpm","pnpm dlx skills add AaravChadha\u002Facstack --skill migrate-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-check\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fgate-shape.md","REFERENCE","参考文档",3538,"https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-check\u002Freferences\u002Fgate-shape.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fsql-classification.md",3114,"https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-check\u002Freferences\u002Fsql-classification.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M79R3MBE63G66XVKHV652YAD","why","Decision archaeology - answers why the code, config, or plan is the way it is by searching the record in a fixed order: BRIEF constraints, dated PLAN decisions, JOURNAL entries, then git history. Stops at the first real answer, cites it with a date, and says no recorded rationale rather than inventing one. Use when someone asks why something is this way, why a choice was made, or where a decision is written down.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M79R3G7EA313SYFS30H1K51A","verify","Audit a completion claim made by someone else - another session, agent, or teammate - against the running system rather than the diff. Re-derives what the claim's acceptance demands, runs it, and returns CONFIRMED, OVERSTATED, FALSE or UNVERIFIABLE with the command and its output. Never fixes, never edits the claim or the acceptance. Use when handed a \"done\", \"all green\", \"merged\" or \"it works\" you did not produce yourself.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M79R3CPD2F05EKE9N8XCMM90","triage","Backlog hygiene sweep - stale items, duplicate pairs, missing acceptance criteria, unblocked-but-unassigned work, and milestone burn, delivered as a report first with only user-approved actions applied. Works on GitHub Issues in tickets mode and on PLAN.md checkboxes in document mode. Use when the user asks to triage, groom, or clean up the backlog or the plan's open tasks.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M79R395S4TS1XENQWWCSBT56","ticket","Capture a brain-dump as a well-formed work item - verb-first title, acceptance criteria, file paths when known, an out-of-scope line. Files a GitHub issue in tickets mode or appends a numbered PLAN.md task in document mode; unknowns are marked TBD, never invented. Use when the user brain-dumps an idea, bug, or task to capture for later, or asks to ticket, file, or note something as work.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fticket\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M79R358JKQ1EB3TQKT2MPSB6","ship","Branch-level release with five gates before the act - clean-state, tests, eval-vs-target, docs drift, and attribution sweep; any failing gate stops the release with its output. Then push, and under push: branch-pr open a report-shaped PR wiring the issue-closing reference in tickets mode or PLAN task IDs in document mode. Use when the user asks to ship, release, cut, or open the PR for a feature or branch.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M79R2ZXGVB7W1J8ZH8TRGWDN","secure","Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high\u002Fmedium\u002Flow confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization\u002Fcrypto\u002Ftransport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fsecure\u002FSKILL.md",[],[]]