[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KKWEXRJDTB6CB7PN33XSWT":3,"skill-same:01M6KKWEXRJDTB6CB7PN33XSWT":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":58},"01M6KKWEXRJDTB6CB7PN33XSWT","ns-gs-restack-resolve",null,"Drive the local `ns gs restack-resolve` conflict-resolution workflow.","nseng-ai\u002Fns","nseng-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273792438?v=4","01M6KKN105A07WPV2TZKZXZGQF","nseng.ai","01M6KKN14MDSR9VF9739AWXG8M",2,"MIT","https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns\u002Fblob\u002Fmaster\u002Fskills\u002Fincubating\u002Fgs\u002Fns-gs-restack-resolve\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31],"ns gs restack resolve","workflow","drive","local","conflict","resolution","true","conflict-resolution","2026-11-10 10:12:30",false,"---\nname: ns-gs-restack-resolve\ndisable-model-invocation: true\ndescription: \"Drive the local `ns gs restack-resolve` conflict-resolution workflow.\"\n---\n\n# ns-gs-restack-resolve\n\nDrive the local gh-stack restack-resolve workflow from the current worktree.\nUse **downstack inter-branch scope** by default; use **full inter-branch scope**\nonly when the user explicitly asks for the whole stack.\n\nThis skill is the parent-session **driver**: it owns the initial CLI run, scope\nnarration, sequential subagent dispatch, interpretation of structured CLI and\nrepository evidence, final checks, and user-facing escalation. All resolution\npolicy for each conflict stop belongs to the **engine**,\n`code-resolve-merge-conflicts` at\n`skills\u002Fincubating\u002Fcode\u002Fcode-resolve-merge-conflicts\u002FSKILL.md`, configured only\nthrough the driver parameters in **Conflict subagent prompt**. The engine's safe\ncategories, verification gate, edit and staging rules, escalation payload, and\nabort policy apply as written there.\n\n## Scope\n\n- Generic or ambiguous restack intent means `RESTACK_SCOPE=downstack`.\n- Explicit whole-stack intent means `RESTACK_SCOPE=full`.\n- \"Downstack\" is the provider's narrower **local inter-branch** operation from\n  the current branch (ancestors + current); \"full\" is its wider whole-stack\n  local inter-branch operation.\n  Neither fetches, updates, or integrates trunk, and neither pushes or\n  reconciles GitHub state.\n- Scope is selected once, before any mutation, and carried as narration for the\n  rest of the run. After an interruption, keep the originally selected scope.\n\n## Mutation whitelist\n\nThe only mutations this workflow performs, all inside a conflict subagent:\n\n1. Stage an engine-accepted resolution.\n2. Run the continuation command, `ns gs restack-resolve --yes --format json`,\n   at most once per conflict stop.\n\nEverything else — abort, raw `git rebase --continue`, provider-private\noperations, Graphite, Slot release, a second start command — is outside the\nworkflow. When evidence is malformed, contradictory, ambiguous, or positively\nidentifies a conflict outside the selected scope, the correct move is to stop\nand report; scope is never reconstructed by topology inspection.\n\nThe audit invariant:\n\n> one conflict stop = one engine run = one CLI continuation = one fresh\n> same-worktree subagent\n\nIf a child's one continuation reaches another conflict stop, that new stop\nbelongs to a fresh child launched by the parent.\n\n## Workflow\n\n### 1. Select and state scope\n\nSet `RESTACK_SCOPE`. Tell the user the selected scope is local inter-branch\nonly and leaves trunk, pushes, and GitHub state untouched.\n\n### 2. Run the initial fast path\n\nIn the parent session, run exactly one structured command:\n\n```bash\nns gs restack-resolve --yes --format json\n# or, only for explicit whole-stack intent:\nns gs restack-resolve --full --yes --format json\n```\n\nRead the structured JSON envelope and branch on its `data`, not exit code\nalone:\n\n- `data.outcome=completed` → **Completion**.\n- `data.outcome=conflict-stopped` with `data.currentOperation=rebase` and\n  nonempty `data.unmergedPaths` → refresh with `git status`, then **Conflict\n  loop**.\n- `data.outcome=refused` → report the bounded diagnostic and final recovery\n  instruction, and stop there.\n- Missing, malformed, or contradictory fields → stop as ambiguous, without\n  mutation.\n\nTwo pre-existing-state branches: a recognized conflict stop can make this first\ncall a non-mutating refusal with recovery `resolve-conflicts` — once the\nenvelope and fresh `git status` agree the rebase is stopped at unresolved\npaths, enter the conflict loop. A resolved-and-staged interruption may make the\nfirst call the single continuation for that stop; treat its result normally. An\nalready-active operation is resumed through the conflict loop, not through a\nsecond start command.\n\n### 3. Conflict loop\n\nEvery continuation in this loop is `ns gs restack-resolve --yes --format json`\n— continuation resumes provider state and never takes `--full`. For each\nobserved conflict stop:\n\n1. In the parent, reconcile the latest structured CLI result with fresh\n   `git status`. Require an active rebase and the same unresolved paths; if the\n   evidence disagrees or cannot identify one current stop, escalate as\n   ambiguous without mutation.\n2. Launch exactly one fresh subagent in this same worktree with the prompt\n   below, sequentially — one child per stop.\n3. When it returns, reread `git status` and the child's structured CLI\n   evidence in the parent; the child's prose summary is not authority.\n4. Classify the observed result:\n   - **advanced:** the child's one continuation reached a later conflict stop;\n     launch one fresh child for that stop.\n   - **completed:** go to **Completion**.\n   - **escalation:** present the engine's escalation payload to the user and\n     leave the operation stopped at this stop; the user's decision drives what\n     happens next.\n   - **bail or ambiguity:** stop and report what is resolved, what remains,\n     the original scope, and the exact repository\u002FCLI state, leaving the\n     operation stopped.\n\nCarry any `unverified` behavior or pre-existing-failure label forward\nunchanged in later prompts and reports until independently verified.\n\n## Conflict subagent prompt\n\nFill in `RESTACK_SCOPE` from the parent-selected original scope.\n\n```text\nYou are resolving exactly one conflict stop in an ns GS restack that is already\nin progress in this same worktree.\n\nDriver parameters (orchestrator-decided):\n- Original RESTACK_SCOPE: \u003Cfull|downstack> local inter-branch scope — narration\n  and safety context only; the continuation command does not encode it\n- Continue command: ns gs restack-resolve --yes --format json\n- Extra bail-out condition: repository\u002FCLI evidence cannot unambiguously show\n  this same active rebase conflict stop or the continuation outcome, or it\n  positively identifies a conflict outside the original RESTACK_SCOPE\n- Post-completion checks: return the complete structured CLI envelope plus\n  fresh git status to the parent; the parent owns final checks\n- Escalation channel: return-to-parent\n\nFollow skills\u002Fincubating\u002Fcode\u002Fcode-resolve-merge-conflicts\u002FSKILL.md as the sole\nconflict-resolution policy authority with those driver parameters.\n\nYour mutation whitelist:\n1. Stage a resolution the engine accepts.\n2. Run the continue command at most once, and only when the engine permits\n   continuation.\nEverything else — abort, skip, raw Git continue, a start command, `gh stack`,\nprovider-private operations, Graphite, Slot release — is outside your task. If\nthe continuation reaches a later conflict stop, leave it untouched and report\noutcome=advanced. If state is ambiguous, stop without staging, continuing, or\naborting, and report outcome=bail.\n\nOutput contract: end with this delimited result block and fill every line:\n--- GS CONFLICT SUBAGENT RESULT ---\noutcome: advanced | completed | escalation | bail\noriginal_scope: full | downstack\nfiles_resolved: \u003Cpaths or none>\ncontinuation_ran: yes | no\ncli_evidence: \u003Ccomplete structured envelope, or none with reason>\nrepository_evidence: \u003Cfresh git status summary>\nengine_report: \u003Cper the engine's evidence rules: safe categories used,\nverification commands and results, and any behavior or pre-existing-failure\nclaims with their observed\u002Funverified labels>\nsummary: \u003Cconcise summary>\n\nFor outcome=escalation, include the engine's complete escalation payload.\n--- END GS CONFLICT SUBAGENT RESULT ---\n```\n\n## Completion\n\nReread the completed structured CLI envelope in the parent and run:\n\n```bash\ngit status\ngit log --oneline -5\n```\n\nRequire `data.outcome=completed`, `data.currentOperation=none`, no unmerged\npaths, and a clean `git status`. Report the original full\u002Fdownstack local\ninter-branch scope and whether any conflicts were resolved, and remind the\nuser that completion left trunk, pushes, and GitHub state untouched.\n\nIf generated files were accepted during conflict resolution, follow the\nengine's regeneration policy before calling the overall workflow done. If final\nCLI and repository evidence disagree, stop and report ambiguity.\n\n## Bail-out\n\nUse the engine's bail-out policy plus this driver's ambiguity condition. Leave\nthe operation stopped and report: resolved files, remaining conflicts, original\nscope, the last CLI invocation and structured outcome, and fresh `git status`.\nDescribe only the stopped or ambiguous state that is observed.\n","# ns-gs-restack-resolve\n\nDrive the local gh-stack restack-resolve workflow from the current worktree.\nUse **downstack inter-branch scope** by default; use **full inter-branch scope**\nonly when the user explicitly asks for the whole stack.\n\nThis skill is the parent-session **driver**: it owns the initial CLI run, scope\nnarration, sequential subagent dispatch, interpretation of structured CLI and\nrepository evidence, final checks, and user-facing escalation. All resolution\npolicy for each conflict stop belongs to the **engine**,\n`code-resolve-merge-conflicts` at\n`skills\u002Fincubating\u002Fcode\u002Fcode-resolve-merge-conflicts\u002FSKILL.md`, configured only\nthrough the driver parameters in **Conflict subagent prompt**. The engine's safe\ncategories, verification gate, edit and staging rules, escalation payload, and\nabort policy apply as written there.\n\n## Scope\n\n- Generic or ambiguous restack intent means `RESTACK_SCOPE=downstack`.\n- Explicit whole-stack intent means `RESTACK_SCOPE=full`.\n- \"Downstack\" is the provider's narrower **local inter-branch** operation from\n  the current branch (ancestors + current); \"full\" is its wider whole-stack\n  local inter-branch operation.\n  Neither fetches, updates, or integrates trunk, and neither pushes or\n  reconciles GitHub state.\n- Scope is selected once, before any mutation, and carried as narration for the\n  rest of the run. After an interruption, keep the originally selected scope.\n\n## Mutation whitelist\n\nThe only mutations this workflow performs, all inside a conflict subagent:\n\n1. Stage an engine-accepted resolution.\n2. Run the continuation command, `ns gs restack-resolve --yes --format json`,\n   at most once per conflict stop.\n\nEverything else — abort, raw `git rebase --continue`, provider-private\noperations, Graphite, Slot release, a second start command — is outside the\nworkflow. When evidence is malformed, contradictory, ambiguous, or positively\nidentifies a conflict outside the selected scope, the correct move is to stop\nand report; scope is never reconstructed by topology inspection.\n\nThe audit invariant:\n\n> one conflict stop = one engine run = one CLI continuation = one fresh\n> same-worktree subagent\n\nIf a child's one continuation reaches another conflict stop, that new stop\nbelongs to a fresh child launched by the parent.\n\n## Workflow\n\n### 1. Select and state scope\n\nSet `RESTACK_SCOPE`. Tell the user the selected scope is local inter-branch\nonly and leaves trunk, pushes, and GitHub state untouched.\n\n### 2. Run the initial fast path\n\nIn the parent session, run exactly one structured command:\n\n```bash\nns gs restack-resolve --yes --format json\n# or, only for explicit whole-stack intent:\nns gs restack-resolve --full --yes --format json\n```\n\nRead the structured JSON envelope and branch on its `data`, not exit code\nalone:\n\n- `data.outcome=completed` → **Completion**.\n- `data.outcome=conflict-stopped` with `data.currentOperation=rebase` and\n  nonempty `data.unmergedPaths` → refresh with `git status`, then **Conflict\n  loop**.\n- `data.outcome=refused` → report the bounded diagnostic and final recovery\n  instruction, and stop there.\n- Missing, malformed, or contradictory fields → stop as ambiguous, without\n  mutation.\n\nTwo pre-existing-state branches: a recognized conflict stop can make this first\ncall a non-mutating refusal with recovery `resolve-conflicts` — once the\nenvelope and fresh `git status` agree the rebase is stopped at unresolved\npaths, enter the conflict loop. A resolved-and-staged interruption may make the\nfirst call the single continuation for that stop; treat its result normally. An\nalready-active operation is resumed through the conflict loop, not through a\nsecond start command.\n\n### 3. Conflict loop\n\nEvery continuation in this loop is `ns gs restack-resolve --yes --format json`\n— continuation resumes provider state and never takes `--full`. For each\nobserved conflict stop:\n\n1. In the parent, reconcile the latest structured CLI result with fresh\n   `git status`. Require an active rebase and the same unresolved paths; if the\n   evidence disagrees or cannot identify one current stop, escalate as\n   ambiguous without mutation.\n2. Launch exactly one fresh subagent in this same worktree with the prompt\n   below, sequentially — one child per stop.\n3. When it returns, reread `git status` and the child's structured CLI\n   evidence in the parent; the child's prose summary is not authority.\n4. Classify the observed result:\n   - **advanced:** the child's one continuation reached a later conflict stop;\n     launch one fresh child for that stop.\n   - **completed:** go to **Completion**.\n   - **escalation:** present the engine's escalation payload to the user and\n     leave the operation stopped at this stop; the user's decision drives what\n     happens next.\n   - **bail or ambiguity:** stop and report what is resolved, what remains,\n     the original scope, and the exact repository\u002FCLI state, leaving the\n     operation stopped.\n\nCarry any `unverified` behavior or pre-existing-failure label forward\nunchanged in later prompts and reports until independently verified.\n\n## Conflict subagent prompt\n\nFill in `RESTACK_SCOPE` from the parent-selected original scope.\n\n```text\nYou are resolving exactly one conflict stop in an ns GS restack that is already\nin progress in this same worktree.\n\nDriver parameters (orchestrator-decided):\n- Original RESTACK_SCOPE: \u003Cfull|downstack> local inter-branch scope — narration\n  and safety context only; the continuation command does not encode it\n- Continue command: ns gs restack-resolve --yes --format json\n- Extra bail-out condition: repository\u002FCLI evidence cannot unambiguously show\n  this same active rebase conflict stop or the continuation outcome, or it\n  positively identifies a conflict outside the original RESTACK_SCOPE\n- Post-completion checks: return the complete structured CLI envelope plus\n  fresh git status to the parent; the parent owns final checks\n- Escalation channel: return-to-parent\n\nFollow skills\u002Fincubating\u002Fcode\u002Fcode-resolve-merge-conflicts\u002FSKILL.md as the sole\nconflict-resolution policy authority with those driver parameters.\n\nYour mutation whitelist:\n1. Stage a resolution the engine accepts.\n2. Run the continue command at most once, and only when the engine permits\n   continuation.\nEverything else — abort, skip, raw Git continue, a start command, `gh stack`,\nprovider-private operations, Graphite, Slot release — is outside your task. If\nthe continuation reaches a later conflict stop, leave it untouched and report\noutcome=advanced. If state is ambiguous, stop without staging, continuing, or\naborting, and report outcome=bail.\n\nOutput contract: end with this delimited result block and fill every line:\n--- GS CONFLICT SUBAGENT RESULT ---\noutcome: advanced | completed | escalation | bail\noriginal_scope: full | downstack\nfiles_resolved: \u003Cpaths or none>\ncontinuation_ran: yes | no\ncli_evidence: \u003Ccomplete structured envelope, or none with reason>\nrepository_evidence: \u003Cfresh git status summary>\nengine_report: \u003Cper the engine's evidence rules: safe categories used,\nverification commands and results, and any behavior or pre-existing-failure\nclaims with their observed\u002Funverified labels>\nsummary: \u003Cconcise summary>\n\nFor outcome=escalation, include the engine's complete escalation payload.\n--- END GS CONFLICT SUBAGENT RESULT ---\n```\n\n## Completion\n\nReread the completed structured CLI envelope in the parent and run:\n\n```bash\ngit status\ngit log --oneline -5\n```\n\nRequire `data.outcome=completed`, `data.currentOperation=none`, no unmerged\npaths, and a clean `git status`. Report the original full\u002Fdownstack local\ninter-branch scope and whether any conflicts were resolved, and remind the\nuser that completion left trunk, pushes, and GitHub state untouched.\n\nIf generated files were accepted during conflict resolution, follow the\nengine's regeneration policy before calling the overall workflow done. If final\nCLI and repository evidence disagree, stop and report ambiguity.\n\n## Bail-out\n\nUse the engine's bail-out policy plus this driver's ambiguity condition. Leave\nthe operation stopped and report: resolved files, remaining conflicts, original\nscope, the last CLI invocation and structured outcome, and fresh `git status`.\nDescribe only the stopped or ambiguous state that is observed.\n",{"name":5,"description":7,"disable-model-invocation":37},true,"master","44a56f0d543f274b42239091b35fe4d23855f6b3","skills\u002Fincubating\u002Fgs\u002Fns-gs-restack-resolve",0,"https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns","https:\u002F\u002Fgithub.com\u002Fnseng-ai","Keeping the clankers in check: Nonslop Engineering for AI","2026-10-02 12:48:53",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":37},[48,51,54],{"tool":49,"command":50},"npx","npx skills add nseng-ai\u002Fns --skill ns-gs-restack-resolve",{"tool":52,"command":53},"bunx","bunx skills add nseng-ai\u002Fns --skill ns-gs-restack-resolve",{"tool":55,"command":56},"pnpm","pnpm dlx skills add nseng-ai\u002Fns --skill ns-gs-restack-resolve","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns\u002Fblob\u002Fmaster\u002Fskills\u002Fincubating\u002Fgs\u002Fns-gs-restack-resolve\u002FSKILL.md",[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns\u002Fblob\u002Fmaster\u002Fskills\u002Fincubating\u002Fgs\u002Fns-gs-restack-resolve\u002Fagents\u002Fopenai.yaml",[66,88,117,140,163,174],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":32},"01M6KM3VZ7JC4S6R4KATJ368EH","pr-make-accountable","Interview a PR author to establish shared understanding of intent and design decisions, then co-author the What \u002F Why \u002F Changes PR body with opt-in Requested reviewer focus.","https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic\u002Fprs\u002Fpr-make-accountable\u002FSKILL.md",[],[73,74,75,76,77,78,79,80,81,82,83,84,85,30,86,87],"pr","make","pr make accountable","design","why","reviewer","decisions","interview","intent","focus","shared","co","with","changes","pr body",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":97,"publishedAt":32},"01M6KM3NZCZ86VJ91RSVTRGTJW","typescript-style","Opinionated style guide for strict, portable TypeScript. Use when writing, designing, or reviewing TypeScript: type design, boundary validation, error handling, module architecture, and review discipline.","https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns\u002Fblob\u002Fmaster\u002Fskills\u002Finternal\u002Ftypescript\u002Ftypescript-style\u002FSKILL.md",[94],{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[98,99,100,76,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116],"typescript","style","typescript style","writing","review","architecture","core","error handling","system","Rules","README","use","error-handling","study","module","error","case-study","style guide","for",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":126,"publishedAt":32},"01M6KM3HNY4WY42KMYRPS6KEJZ","typescript-fake-driven-testing","TypeScript fake-driven testing architecture. Use when writing or reviewing TS code with external dependencies, gateway interfaces, real adapters, in-memory fakes, or CLI scenario tests.","https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns\u002Fblob\u002Fmaster\u002Fskills\u002Finternal\u002Ftypescript\u002Ftypescript-fake-driven-testing\u002FSKILL.md",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[127,98,128,129,130,101,131,132,103,133,134,109,135,136,137,138,85,139],"testing","driven","fake driven testing","typescript fake driven testing","cli","memory","code","gateway","dependencies","tests","scenario","Adapters","in-memory",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":32},"01M6KM3AXC2539PENYVZJYKCP9","ns-typescript","TypeScript overlay for ns-style projects. Use when editing or reviewing TS in this repo: tsconfig baseline, pnpm\u002FVitest\u002Foxlint\u002Foxfmt\u002Fnative tsc commands, relative .ts imports, workspace subpath exports, and the exactOptionalPropertyTypes spread idiom. Repo-specific enforcement (test lanes, time seams, style guard) lives in the host repo's AGENTS.md.","https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns\u002Fblob\u002Fmaster\u002Fskills\u002Finternal\u002Ftypescript\u002Fns-typescript\u002FSKILL.md",[],[98,147,148,149,150,151,152,153,109,154,155,156,157,99,158,159,160,116,161,162],"ns typescript","test","guard","vitest","projects","editing","repo","enforcement","references","time","host","oxlint","import","native","alternatives","imports",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":32},"01M6KM36Y5KZ5V48M58MT42AHM","ns-typescript-style-tripwire","Invoke the ns TypeScript style Tripwire against a supplied diff or current branch.","https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns\u002Fblob\u002Fmaster\u002Fskills\u002Finternal\u002Ftypescript\u002Fns-typescript-style-tripwire\u002FSKILL.md",[],[98,170,99,171,172,173,30],"tripwire","ns typescript style tripwire","branch","diff",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":181,"publishedAt":32},"01M6KM313HANS0AV181X37ZM45","skill-management","Manage skills with `npx skills`: add, edit, remove, rename, update, or list skills (local or GitHub), and the nested `skills\u002F\u003Cdisposition>\u002F...\u002F\u003Cname>\u002F` \u002F flat `.agents\u002Fskills\u002F` layout conventions.","https:\u002F\u002Fgithub.com\u002Fnseng-ai\u002Fns\u002Fblob\u002Fmaster\u002Fskills\u002Finternal\u002Fskill-system\u002Fskill-management\u002FSKILL.md",[180],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[182,183,184,185,186,173,187,188,49,27,189,85,190,191,192,193,194,195,30,196],"management","skill management","github","Bash","remove","nested","manage","cat","ln","ls","mkdir","mv","readlink","rg","lock"]