AGENT SKILL

market-pre-push-checks

Use before pushing, merging, or claiming a green tree in dsh-agent-plugins-market, to select the smallest checks that cover the outgoing diff instead of reflexively running the full suite.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 21
Forks
2

01 前言 Front Matter

name
market-pre-push-checks
description
Use before pushing, merging, or claiming a green tree in dsh-agent-plugins-market, to select the smallest checks that cover the outgoing diff instead of reflexively running the full suite.

03 SKILL.md 正文

Market Pre-Push Checks

Run evidence matched to the outgoing diff once, then report only the commands run. CI owns exhaustive coverage; the full pnpm run test locally is reserved for release verification (see market-release) and repository-wide changes.

Steps

  1. Scope the diff. git status --short --branch and git diff <base> --stat; the surface list is the completion criterion for this step.
  2. Map surface to evidence and run the union once:
Outgoing surface Evidence
src/** or tests/** check:refactor + the vitest files mirroring the touched areas (tests/<area>.test.ts)
src/client/** or locales.ts above + every tests/client-*.test.ts
schemas/** above + packages/market-bundle/test/integration/mcp-config.test.ts + packages/market-catalog/test/lsp-spec.test.ts
docs/**, README*, docs-site/** format:check + pnpm --dir docs-site run check:guide && pnpm --dir docs-site run build && pnpm --dir docs-site run check:links (the build+link pair only when site or guide sources changed)
package.json / lockfile pnpm install --frozen-lockfile + check:refactor + check:host-alignment
a new import('@deepseek-ai/dsh-*') above + check:host-alignment (an undeclared host import is a surface that degrades silently)
  1. Re-verify after fixes. Any fix reruns the same command set that failed, nothing more.
  2. Green tree. format:check covers files eslint does not (docs, HTML, fixtures) — include it whenever non-TS files moved, then report the evidence list with the push proposal.

04 同仓库更多 Skills

Sivan757
Sivan757/dsh-agent-plugins-market

verify

Verify that a code change actually does what it's supposed to by running the app and observing behavior. Use when asked to verify a PR, confirm a fix works, test a change manually, check that a feature works, or validate local changes before pushing.

★ 21
Sivan757
Sivan757/dsh-agent-plugins-market

simplify

Review changed code for reuse, quality, and efficiency, then fix any issues found. Use when the user asks to "simplify the code", "clean up the diff", "reduce duplication in my changes", or after finishing a feature before committing.

★ 21
Sivan757
Sivan757/dsh-agent-plugins-market

insight

Analyze this machine's DeepSeek Harness session history and report how sessions actually go — operating style, what works, friction points, and what to try next. Use when the user asks "how have I been using this", "analyze my sessions", "make an insight report", or wants a retrospective.

★ 21
Sivan757
Sivan757/dsh-agent-plugins-market

init

Set up a minimal AGENTS.md (and optionally skills and hooks) for this repo. Use when the user asks to "initialize the project", "generate AGENTS.md", "set up project instructions", or runs /init.

★ 21
Sivan757
Sivan757/dsh-agent-plugins-market

explore

Fast read-only codebase exploration that returns a report instead of filling the main context. Use when the user asks to "explore the codebase", "find where X is handled", "how does Y work", or when a search would take many reads to answer.

★ 21
Sivan757
Sivan757/dsh-agent-plugins-market

automation-recommender

Analyze a codebase and recommend DeepSeek Harness automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their DeepSeek Harness setup, mentions improving DeepSeek Harness workflows, asks how to first set up DeepSeek Harness for a project, or wants to know what DeepSeek Harness features they should use.

★ 21