aicodeking/deepseek-stack

ds-pr-comments

Formats and posts GitHub comments written by an agent on the user's behalf, with clear attribution and no leaked secrets.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-pr-comments

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Make every agent-written comment easy to spot, short and safe to publish.

Steps

  1. Write the reply. Lead with the conclusion. Cite the code line, check, test or reproduction that supports it. Mark what you verified and what is your opinion.
  2. Put this note at the top, with the reply below it:
md
   > [!NOTE]
   > **<model> responding on behalf of <user>**

   Reply text starts here.

Use the model name the harness reports. If it reports none, use the harness name. Use the user's name or GitHub login.

  1. Scan the full comment, including quotes and attachments, for secrets, tokens, private paths and personal data. Remove them.
  2. Preview the final Markdown. Confirm the note and the reply render as two separate blocks.
  3. Post the comment.
  4. Confirm GitHub returned the comment or review URL. Print it.
  5. Resolve a review thread only after its reply posted.

Stop when

  • GitHub returned a URL for each comment you meant to post.
  • A post fails twice. Report the error and do not resolve the thread.

Rules

  • Use the note on top-level comments, inline review comments, replies to bots and people, and dismissal reasons.
  • Do not use it in PR descriptions, commit messages or text the user asked to post word for word.
  • One attribution only. No signature, footer, heading or horizontal rule.
  • No thanks, filler or status updates such as "still working on it".
  • Never guess the model name.
do mesmo repositório

Mais Skills

Todos os Skills
aicodeking
Comunidade

ds-adopt

Takes over an existing PR, branch or agent thread and finishes its original goal while keeping credit for the first contributors. Use when the user says take over, adopt, pick up or finish this PR, or /ds-adopt.

Instalações / 1h
2
GitHub Stars
75
Atualizado
28 de out.
aicodeking
Comunidade

ds-best-of-n

Run N independent attempts at the same task in parallel, pick the strongest as the base, and graft the best parts of the others into it. Use when one attempt at a non-trivial artifact could land on the wrong shape, or for /ds-best-of-n, 'try a few versions', 'best of 3'.

Instalações / 1h
2
GitHub Stars
75
Atualizado
28 de out.
aicodeking
Comunidade

ds-blast-radius

Find what a change could break outside its own diff, then prove the key safety fact by running real code. Use before shipping a risky or untrusted change, for 'what could this break', 'blast radius of X', or /ds-blast-radius.

Instalações / 1h
2
GitHub Stars
75
Atualizado
28 de out.
aicodeking
Comunidade

ds-blueprint

Design the types, function signatures and module layout first, agree on that shape, then implement against it. Use when work is non-trivial and coding straight away would lock in the wrong structure, or for /ds-blueprint, 'design this first', 'architect this'.

Instalações / 1h
2
GitHub Stars
75
Atualizado
28 de out.