Keeps a project's to-do list and memory in GitHub issues — files each finding (from a review, an audit, or the user) as its own issue without duplicates, lists the open issues that bear on the current work, and closes an issue with a comment recording what was wrong, what was tried, what worked, and how it was fixed. Use when review findings or a list of problems should become tracked work (a paper's misleading claims, a codebase's bugs, improvements for later), when starting or resuming work and deciding what to do next, or when a fix has landed and its issue should be closed with a record. Needs the GitHub CLI; warns before posting to a public repository.
Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.
读取 https://funcoding.ai/skills/pedrohcgs/claude-code-my-workflow/issues/install.md ，按里面的步骤帮我安装这个 Skill。
Every problem worth fixing becomes an issue: a claim in the paper that misleads, a table that disagrees with the code, a bug, an improvement for later. The open issues are the to-do list. When a fix lands, the issue is closed with a comment that says what was wrong, what was tried — including what did not work — and how it was fixed. Read back months later, the closed issues are the project's memory: auditable, searchable, and the same on every machine and for every co-author, which a chat transcript or a local notes file is not.
This skill makes the habit cheap. It never posts anything without showing the draft first and getting a yes.
/review-paper, /seven-pass-review, /adjudicate-review, or findings
you list yourself — to turn each confirmed problem into its own issue.file <report|text> — turn findings into issuesThe input is a findings JSON from the review runtime, a review report, or problems described in the conversation.
gh auth status must succeed. Then gh repo view --json visibility,nameWithOwner:
on a PUBLIC repository, say plainly that every issue will be public — unpublished results,
referee-sensitive weaknesses and co-authors' drafts would be visible to anyone — suggest a
private repository for paper work, and create nothing without an explicit yes to that.scripts/file-issue.py (step 5), which runs several searches first:
the title's most distinctive words together, the top three alone in titles, every --search
term you pass (a section name, a table label, a function), and up to three file paths the
issue names — at most eight searches, and any dropped are reported. A match gets a comment on the existing issue (reopen it if the problem is back), not a
new issue.git rev-parse --short HEAD).bug, documentation or enhancement, plus an area label such as paper,
code or slides if the project uses them (create one on first use with gh label create).python3 scripts/file-issue.py --title "…" --body-file <draft> [--label …] [--search "…"].
Exit 3 means it found possible duplicates and created nothing: read each (gh issue view N),
comment on the one that is the same problem, or — if the new issue is distinct from all of
them — re-run with --checked N,M. The issue body then records which searches ran and which
candidates were judged distinct. Exit 2 means the search could not run, and nothing was
created. A raw gh issue create is denied by the issue-guard hook for the same reason.
Report the new numbers.list [topic] — what is opengh issue list --state open --limit 100 --json number,title,labels,updatedAt, filtered to the
topic, section or files at hand, oldest first. End with a suggestion of which issue to take next
and why (blocking others, oldest, smallest). Read-only.
To have every new session start with the open list, set CLAUDE_ISSUES_AT_START=1 (under env
in .claude/settings.local.json for your machine only). The open-issues hook then lists open
issues' numbers and titles — by the owner and collaborators only — at startup. It is off by
default because it calls GitHub on every startup.
close <#N> — close with a recordGather: the issue (gh issue view N --comments), the commits that mention it
(git log --oneline --grep "#N"), and what they changed.
Draft the closing comment:
A small fix (a typo, a stale sentence) gets the short form: what was wrong, the commit, how it
was checked. A defect that can move a result or a number gets the full seven sections of
issue-ledger.md.
After the user's yes: gh issue comment N --body-file <draft>, then gh issue close N. For a
problem that turned out not to be one, gh issue close N --reason "not planned", with the
evidence in the comment.
confidential-data.md).
Describe the problem abstractly; the evidence stays where the data lives. Issues are copied,
emailed and indexed; a DUA does not follow them.Refs #N, never "Closes #N" or "Fixes #N". A merge is a code event; closing
is a judgment that the problem is gone, made with the closing comment.Open an issue for each claim that misleads, each number that disagrees with its source, each figure that is hard to read, each argument a referee will push on. Work the list; close each issue with what you changed and why. Keep paper work in a private repository. Before a submission or an R&R, the closed issues are the response-to-referees raw material, and the open ones are what is left to do.
| Flag | Effect |
|---|---|
--dry-run | Print the drafts and the exact commands; post nothing (scripts/file-issue.py --dry-run still runs the duplicate search). |
gh, or not logged in: stop with the install line (brew install gh / apt install gh)
or gh auth login, and print the drafts so they can be entered by hand.For file: the numbered drafts, then Created #N, #M (or Commented on #K — already tracked).
For list: one line per issue — number, title, labels, days since update — and the suggestion.
For close: the comment as posted and Closed #N.
scripts/file-issue.py — the duplicate check every new issue goes through; issue-guard.py — the hook that keeps it the only route; open-issues.py — the opt-in startup list.issue-ledger.md — what gets an issue, the evidence standard, the closing comment.progress-reports.md — issues are the defect memory; session logs and MEMORY.md hold the rest./adjudicate-review — decides which findings are real before they are filed./review-paper and /seven-pass-review — produce findings worth filing./adjudicate-review./triage-inbox.glab, by hand.
anthropics/skills180kUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Docs & office
anthropics/skills180kAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.
Docs & office
anthropics/skills180kGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Docs & office
anthropics/skills180kUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Docs & office
anthropics/skills180kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.
Docs & office
anthropics/skills180kCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Docs & office