CommunityRédaction et éditiongithub.com

Varnan-Tech/opendirectory

Lit les tâches Linear et les commits GitHub de la veille, formate une mise à jour de standup (fait / en cours / blocages) et la publie sur Slack.

Qu'est-ce que opendirectory ?

Cette compétence automatise la rédaction du standup quotidien en rassemblant automatiquement les tâches Linear et les commits GitHub de la veille. Elle catégorise les tâches Linear selon leur état (terminé, en cours, annulé) et les commits GitHub après filtrage des merges et déduplication. Le résultat est formaté selon une structure stricte (Fait / En cours / Bloqueurs) sans pronoms personnels, et peut être publié directement sur Slack via un webhook ou affiché pour copie manuelle. Utile pour les développeurs utilisant Linear, GitHub et Slack, elle nécessite que les variables d'environnement LINEAIR_API_KEY, SLACK_WEBHOOK_URL et éventuellement GITHUB_REPO soient définies.

Compatible avec✓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 Rédaction et édition skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Tue le standup

Lit les tâches Linear et les commits GitHub de la veille. Formate une mise à jour de standup. Publie-la sur Slack.


Étape 1 : Vérification de la configuration

Confirme que les variables d'environnement requises sont définies :

echo "LINEAR_API_KEY: ${LINEAR_API_KEY:+définie}"
echo "SLACK_WEBHOOK_URL: ${SLACK_WEBHOOK_URL:+définie}"
echo "GITHUB_REPO: ${GITHUB_REPO:-non définie}"
echo "GITHUB_USERNAME: ${GITHUB_USERNAME:-non définie}"

Si LINEAR_API_KEY est manquante : Arrête-toi. Dis à l'utilisateur : "LINEAR_API_KEY est requise. Obtiens-la depuis Linear → Paramètres → API → Clés API personnelles. Ajoute-la à ton fichier .env."

Si SLACK_WEBHOOK_URL est manquant : Arrête-toi. Dis à l'utilisateur : "SLACK_WEBHOOK_URL est requis. Crée un webhook entrant sur api.slack.com/apps → Ton application → Webhooks entrants. Ajoute-le à ton fichier .env."

Si GITHUB_REPO est manquant : Continue. Les commits GitHub seront ignorés. Note-le à l'utilisateur.


Étape 2 : Récupération de l'activité Linear

Calcule la date d'hier au format ISO 8601 (ex : 2026-04-09T00:00:00.000Z).

Obtenir l'ID utilisateur actuel :

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 } }"}'

Extrais le champ id de la réponse. Stocke-le comme LINEAR_USER_ID.

Récupérer les tâches qui me sont assignées, mises à jour depuis hier :

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": "HIER_ISO", "userId": "LINEAR_USER_ID"}
  }'

Catégoriser les tâches :

  • completedAt non null → Fait
  • state.name est "In Progress", "Started" ou "In Review" → En cours
  • state.name est "Cancelled" → ignorer
  • state.name est "Todo" ou "Backlog" → ignorer (non travaillé)

Si zéro tâche : note "Aucune activité Linear trouvée hier."


Étape 3 : Récupération des commits GitHub

Ignore cette étape silencieusement si GITHUB_REPO n'est pas défini.

Si GITHUB_REPO est défini :

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

Traiter les commits :

  • Extrais la première ligne de chaque message de commit (tout ce qui précède la première nouvelle ligne)
  • Ignorer les commits de merge : supprimer tout message commençant par "Merge"
  • Dédupliquer par texte du message

Si GITHUB_REPO est défini mais retourne zéro commit : note "Aucun commit trouvé hier."


Étape 4 : Formatage du standup

Lis references/standup-format.md en entier avant d'écrire.

Produis le standup dans cette structure exacte :

**Fait**
- [ENG-123] Titre de la tâche terminée
- correctif : message de commit ici

**En cours**
- [ENG-124] Titre de la tâche en cours

**Bloqueurs**
Aucun bloqueur.

Règles issues de standup-format.md :

  • Pas de pronoms à la première personne ("je", "nous")
  • Passé pour les éléments Fait, présent continu pour les éléments En cours
  • Chaque élément Linear utilise le format [IDENTIFIANT] Titre
  • Chaque commit GitHub utilise la première ligne du message de commit
  • Si aucun élément Fait : écris "Rien de terminé." sous Fait
  • Si aucun élément En cours : écris "Rien en cours." sous En cours
  • Si aucun bloqueur : écris "Aucun bloqueur."
  • Moins de 200 mots au total

Étape 5 : Publication sur Slack ou sortie

Présente le standup formaté à l'utilisateur.

Demande : "Publier ceci sur Slack, ou simplement afficher ?"

Sur confirmation de publication :

curl -s -X POST "$SLACK_WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -d '{
    "blocks": [
      {
        "type": "section",
        "text": {
          "type": "mrkdwn",
          "text": "*Standup — DATE_ICI*\n\n*Fait*\nÉLÉMENTS\n\n*En cours*\nÉLÉMENTS\n\n*Bloqueurs*\nÉLÉMENTS"
        }
      }
    ]
  }'

Passe le corps via un fichier temporaire ou heredoc pour éviter les problèmes de citation du shell avec les caractères spéciaux dans les messages de commit ou les titres de tâches :

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

Après publication : "Standup publié."

Sur "afficher seulement" : Affiche le standup dans un bloc de code pour copier-coller.

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.

Skills associés