1-triage-issues

stickerdaniel · ИнструментиЕзик на описанието

Triage backlog, scan open issues, rank what to tackle first, or which PRs are production-ready.

Оригинален текст · няма потвърден превод на български

Платформи: Не са посочениНиво: Не е посоченоВ индекса: 22.09.2026 г.Обновен в GitHub: 21.09.2026 г.

Теми: ai-agents · anthropic · chatgpt · chatgpt-desktop · claude · claude-ai · claude-code · claude-desktop · desktop-extension · dxt · linkedin · linkedin-api · linkedin-mcp · linkedin-profile-scraper · linkedin-scraper

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md

GitHub хранилище

Звезди на репото: 3592
Лиценз: Apache-2.0
Последна проверка на записа: 22.09.2026 г.

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add stickerdaniel/linkedin-mcp-server

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

Triage open issues and PRs

Turn the live state of stickerdaniel/linkedin-mcp-server into a maintainer priority list. Read-only. No checkout, no labels, no comments, no closure, no reproduction.

Reproduction belongs in /2-repro-issue. PR verification belongs in /3-verify-pr-fix.

Inputs

$ARGUMENTS is optional. If set, treat as a label name (bug, enhancement) or freetext filter. Otherwise scan everything open.

1. Gather

REPO=stickerdaniel/linkedin-mcp-server

# Issues  (gh calls the reactions field `reactionGroups`, not `reactions`)
gh issue list --repo $REPO --state open --limit 200 \
  --json number,title,labels,createdAt,updatedAt,author,comments,reactionGroups,body

# PRs
gh pr list --repo $REPO --state open --limit 100 \
  --json number,title,labels,createdAt,updatedAt,author,mergeable,mergeStateStatus,statusCheckRollup,additions,deletions,changedFiles,reviewDecision,isDraft,headRepositoryOwner

# Cross-link issues ↔ PRs via body references
gh search prs --repo $REPO --state open --json number,body,title --limit 100

Build a map issue_number → [referencing_pr_numbers] by scanning PR bodies for Closes #, Fixes #, Resolves #, plain #N.

If $ARGUMENTS is given, filter both lists before scoring.

Read each issue body and its comments, including linked canonical issues.

2. Packet admission

Before severity, age, reach, or contributor ranking, classify every open issue.

Packet state	Maintainer action
Material evidence missing	Recommend `needs more info` with the specific missing fields. Exclude it from the reproduction shortlist. Existing labels alone do not prove completeness.
Evidence supplied after a request	Read the new evidence. Recommend removing `needs more info` only when it resolves the material gap. A new comment does not automatically clear the label.
Same underlying report as a canonical issue	Note unique reviewed evidence for the canonical issue. Recommend a `Duplicate of #N` comment and a separate close, each with an explicit yes. Do not post or close here.
Evaluable bug or feature	Continue to scoring. Completeness is not a promise of implementation.
Source evidence supports a narrower claim than the reporter's explanation	State that narrower finding. Ask for targeted missing evidence only if the next decision needs it.

Целият SKILL.md в GitHub