CommunityEscrita e Ediçãogithub.com

Varnan-Tech/opendirectory

Lê as issues do Linear e os commits do GitHub de ontem para o usuário autenticado, formata uma atualização de standup (feito / fazendo / bloqueios) e a publica no Slack.

O que é opendirectory?

Este skill automatiza a criação de atualizações diárias de standup para desenvolvedores que usam Linear e GitHub. Ele busca todas as issues do Linear atribuídas ao usuário que foram atualizadas no dia anterior, bem como os commits do GitHub do usuário em um repositório configurado. O skill então formata essas informações em uma estrutura padronizada de 'Feito / Fazendo / Bloqueios', seguindo regras de formatação, e pergunta ao usuário se deseja publicá-la no Slack via webhook ou apenas exibir o resultado. É útil para eliminar o trabalho manual de lembrar e escrever o standup todos os dias, garantindo que as atualizações sejam consistentes e baseadas em dados reais de trabalho. Ele é ativado por comandos como 'write my standup' ou 'post standup' e suporta as plataformas Linear, GitHub e Slack.

Funciona com✓Claude Code~Codex CLI~Cursor✓Gemini CLI
npx skills add https://github.com/Varnan-Tech/opendirectory/tree/main/skills/kill-the-standup

Installed? Explore more Escrita e Edição skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Kill the Standup

Lê as issues de ontem do Linear e os commits do GitHub. Formata uma atualização de standup. Publica no Slack.


Passo 1: Verificação de Configuração

Confirme se as variáveis de ambiente necessárias estão definidas:

echo "LINEAR_API_KEY: ${LINEAR_API_KEY:+set}"
echo "SLACK_WEBHOOK_URL: ${SLACK_WEBHOOK_URL:+set}"
echo "GITHUB_REPO: ${GITHUB_REPO:-não definido}"
echo "GITHUB_USERNAME: ${GITHUB_USERNAME:-não definido}"

Se LINEAR_API_KEY estiver faltando: Pare. Diga ao usuário: "LINEAR_API_KEY é obrigatório. Obtenha-a em Linear → Configurações → API → Chaves de API pessoais. Adicione-a ao seu arquivo .env."

Se SLACK_WEBHOOK_URL estiver faltando: Pare. Diga ao usuário: "SLACK_WEBHOOK_URL é obrigatório. Crie um Webhook de Entrada em api.slack.com/apps → Seu App → Webhooks de Entrada. Adicione-o ao seu arquivo .env."

Se GITHUB_REPO estiver faltando: Continue. Os commits do GitHub serão ignorados. Notifique o usuário sobre isso.


Passo 2: Buscar Atividade do Linear

Calcule a data de ontem no formato ISO 8601 (ex.: 2026-04-09T00:00:00.000Z).

Obter ID do usuário atual:

curl -s -X POST https://api.linear.app/graphql \
  -H "Authorization: Bearer $LINEAR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "query { viewer { id name email } }"}'

Extraia o campo id da resposta. Armazene como LINEAR_USER_ID.

Buscar issues atribuídas a mim, atualizadas desde ontem:

curl -s -X POST https://api.linear.app/graphql \
  -H "Authorization: Bearer $LINEAR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "query($since: DateTime!, $userId: ID!) { issues(first: 50, filter: { assignee: { id: { eq: $userId } } updatedAt: { gte: $since } }) { edges { node { identifier title state { name } url completedAt updatedAt createdAt } } } }",
    "variables": {"since": "YESTERDAY_ISO", "userId": "LINEAR_USER_ID"}
  }'

Categorizar issues:

  • completedAt não é nulo → Feito
  • state.name é "In Progress", "Started" ou "In Review" → Fazendo
  • state.name é "Cancelled" → pular
  • state.name é "Todo" ou "Backlog" → pular (não trabalhadas)

Se zero issues: anote "Nenhuma atividade do Linear encontrada para ontem."


Passo 3: Buscar Commits do GitHub

Ignore esta etapa silenciosamente se GITHUB_REPO não estiver definido.

Se GITHUB_REPO estiver definido:

gh api "repos/$GITHUB_REPO/commits?author=${GITHUB_USERNAME:-$(gh api user --jq .login)}&since=YESTERDAY_ISO&per_page=30" \
  --jq '[.[] | {message: .commit.message, url: .html_url}]'

Processar commits:

  • Extraia a primeira linha de cada mensagem de commit (tudo antes da primeira quebra de linha)
  • Pule commits de merge: descarte mensagens que começam com "Merge"
  • Desduplique por texto da mensagem

Se GITHUB_REPO estiver definido mas retornar zero commits: anote "Nenhum commit encontrado ontem."


Passo 4: Formatar Standup

Leia references/standup-format.md por completo antes de escrever.

Produza o standup exatamente nesta estrutura:

**Feito**
- [ENG-123] Título da issue concluída
- fix: mensagem do commit aqui

**Fazendo**
- [ENG-124] Título da issue em andamento

**Bloqueios**
Nenhum bloqueio.

Regras do standup-format.md:

  • Sem pronomes de primeira pessoa ("eu", "nós")
  • Pretérito para itens Feitos, presente contínuo para itens Fazendo
  • Cada item do Linear usa o formato [IDENTIFICADOR] Título
  • Cada commit do GitHub usa a primeira linha da mensagem do commit
  • Se não houver itens Feitos: escreva "Nada concluído." sob Feito
  • Se não houver itens Fazendo: escreva "Nada em andamento." sob Fazendo
  • Se não houver bloqueios: escreva "Nenhum bloqueio."
  • Menos de 200 palavras no total

Passo 5: Publicar no Slack ou Exibir

Apresente o standup formatado ao usuário.

Pergunte: "Publicar isso no Slack ou apenas exibir?"

Ao confirmar a publicação:

curl -s -X POST "$SLACK_WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -d '{
    "blocks": [
      {
        "type": "section",
        "text": {
          "type": "mrkdwn",
          "text": "*Standup — DATA_AQUI*\n\n*Feito*\nITENS\n\n*Fazendo*\nITENS\n\n*Bloqueios*\nITENS"
        }
      }
    ]
  }'

Passe o corpo via um arquivo temporário ou heredoc para evitar problemas de citação do shell com caracteres especiais em mensagens de commit ou títulos de issues:

cat > /tmp/standup-payload.json << 'ENDJSON'
{
  "blocks": [
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "CONTEUDO_STANDUP_AQUI"
      }
    }
  ]
}
ENDJSON
curl -s -X POST "$SLACK_WEBHOOK_URL" -H "Content-Type: application/json" -d @/tmp/standup-payload.json

Após publicar: "Standup publicado."

Em "apenas exibir": Imprima o standup em um bloco de código para copiar e colar.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

Varnan-Tech/opendirectory

Use when the user asks to generate a blog cover image, thumbnail, or article header. Automatically uses modern typography, brand logos, and Google Search grounding to create beautiful 16:9 images with Gemini 3.1 Flash Image Preview.

Varnan-Tech/opendirectory

World-class brand strategist and naming expert. Uses an interrogation-led discovery phase to extract your brand's DNA, then applies scientific naming frameworks (Phonosemantics) and automated multi-TLD domain checking.

Varnan-Tech/opendirectory

Use when the user asks to generate or update a project's CLAUDE or AGENTS context file from a codebase scan. Writes a focused file under 100 lines containing only the non-obvious build commands, conventions, and gotchas Claude Code needs.

Varnan-Tech/opendirectory

Use when the user wants to verify cold emails, enrich a lead list, or autonomously guess email addresses from a CSV using ValidEmail.co or the open-source Reacher engine.

Varnan-Tech/opendirectory

Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.

Varnan-Tech/opendirectory

Give it your product URL or description. It finds your top 5 competitors, runs three-track PR research across all of them (editorial, podcasts, communities), identifies which channels appear most frequently, looks up the journalist or host for each, and returns a tiered outreach list with story angles and ready-to-send cold pitch drafts tailored to your product. Use when asked to find PR opportunities, discover where competitors got featured, build a media outreach list, find which journalists cover my space, or get pitch templates for press coverage.

Varnan-Tech/opendirectory

Generate high-converting, deep-dive growth case studies in MDX format. Use this skill when asked to write a case study or blog post about a company's growth, tech stack, or product-led strategy. It handles the full pipeline (researching the company via Tavily, generating a 16:9 cover image, quality checking the draft, uploading assets to cloud storage, and pushing directly to the target repository).

Varnan-Tech/opendirectory

Scans your project for outdated npm, pip, Cargo, Go, or Ruby packages. Runs a CVE security audit. Fetches changelogs, summarizes breaking changes with Gemini, and opens one PR per risk group (patch, minor, major). Includes Diagnosis Mode for install conflicts. Use when asked to update dependencies, check for outdated packages, open dependency PRs, scan for package updates, audit for CVEs, or flag breaking changes in upgrades. Trigger when a user says "check for outdated packages", "update my dependencies", "open PRs for dependency updates", "scan for CVEs", or "which packages need upgrading".

Varnan-Tech/opendirectory

Generates and updates README.md and API reference docs by reading your codebase's functions, routes, types, schemas, and architecture. Uses graphify to build a knowledge graph first, then writes accurate docs from it. Use when asked to write docs, generate a README, document an API, update stale docs, create an API reference from code, add an architecture section, or document a project in any language. Trigger when a user says their docs are missing, outdated, or wants to document their codebase without writing it manually.

Varnan-Tech/opendirectory

Evaluates expired domain candidates against a target niche, scores them by topical relevance, historical activity level, and history cleanliness, then outputs a ranked shortlist with explainable reasoning and risk flags.

Varnan-Tech/opendirectory

Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked by impact × effort, and sketches an ideal README. Trigger when user says "roast my repo", "audit my README", "dx audit", "developer experience review", "score my GitHub project", "before launch checklist", or "make my repo shareable".

Varnan-Tech/opendirectory

Drafts and designs a complete HTML email newsletter from a topic or content brief. Outputs paste-ready HTML for Loops, Mailchimp, Beehiiv, Resend, or any standard email platform. Includes subject line options and plain-text fallback. Trigger when a user says "write a newsletter", "draft an email newsletter", "create an HTML email", "design an email for my subscribers", or "write a newsletter about [topic]".

Varnan-Tech/opendirectory

Takes a GitHub PR URL or the current branch and writes a plain-English explanation of what it does and why, then posts it as a PR comment. Use when asked to explain a PR, summarize a pull request, write a plain-English description of a PR, add a summary comment to a PR, or understand what a PR changes. Trigger when a user says "explain this PR", "summarize this pull request", "what does this PR do", "add a comment explaining the PR", or shares a GitHub PR URL and asks what it does.

Varnan-Tech/opendirectory

Audit how often LLMs recommend your brand vs competitors and generate a GEO action plan.

Varnan-Tech/opendirectory

Takes a competitor's public GitHub repo URL, fetches their open issues via the GitHub REST API, filters noise locally, clusters issues into 6 demand categories, computes a demand score per issue and per cluster, and outputs a ranked demand gap report with a GTM messaging brief. Use when asked to scan a competitor's GitHub issues, find what their users are begging for, turn GitHub complaints into product positioning, identify competitor feature gaps, or generate messaging from real user demand. Trigger when a user says "scan competitor issues", "what are users asking for on X repo", "find demand gaps in Y", "turn GitHub issues into messaging", or "what should I build based on competitor complaints".

Varnan-Tech/opendirectory

Find recurring confusion in your repo's GitHub Discussions, rank it by urgency, and draft the actual docs fixes and content angles — with verbatim community quotes and source links as evidence.

Varnan-Tech/opendirectory

SEO keyword research workflow for blog generation using Google Trends data. Use when writing blog posts, planning content calendars, or optimizing articles for search engines. Finds breakout keywords, builds content structure, and generates SEO-optimized blog outlines targeting tech and developer audiences.

Varnan-Tech/opendirectory

Generates a professionally designed case study PDF for B2B SaaS sales and marketing. Supports 7 page layouts, 9 style presets, 1-4 page output. Trigger when user says "create a case study", "write a customer story", "make a case study PDF", "design a success story", "turn this customer win into a PDF".

Varnan-Tech/opendirectory

Generates data visualization charts (bar, line, area, pie, doughnut, scatter, radar, treemap) as PNG using Apache ECharts v6. 1080×1080px default, 5 style presets, highlight annotations. Trigger when user says "create a chart", "visualize data", "make a bar chart", "line graph", "pie chart", "data visualization", "chart this data", "plot", "graph", or "visualize these numbers".

Varnan-Tech/opendirectory

Fetches low-star App Store and Google Play reviews, clusters them into broken-promise patterns, and generates a ranked copy brief with positioning opportunities.

Habilidades Relacionadas