跳到正文
cccskills
免费在 GitHub 公开

proofread

Read-only proofreading pass over lecture `.tex` or `.qmd` files. Checks grammar, typos, overflow, terminology consistency, and academic writing quality; produces a report without editing. Use when user says "proofread", "check for typos", "look for grammar issues", "copy-edit this", "any writing errors?", or before a lecture release.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Proofread Lecture Files

Run the proofreading protocol on lecture files. This produces a report of all issues found WITHOUT editing any source files.

Steps

  1. Identify files to review:

    • If $ARGUMENTS is a specific filename: review that file only
    • If $ARGUMENTS is "all": review all lecture files in Slides/ and Quarto/
  2. For each file, launch the proofreader agent that checks for:

    GRAMMAR: Subject-verb agreement, articles (a/an/the), prepositions, tense consistency TYPOS: Misspellings, search-and-replace artifacts, duplicated words OVERFLOW: Overfull hbox (LaTeX), content exceeding slide boundaries (Quarto) CONSISTENCY: Citation format, notation, terminology ACADEMIC QUALITY: Informal language, missing words, awkward constructions

  3. Produce a detailed report for each file listing every finding with:

    • Location (line number or slide title)
    • Current text (what's wrong)
    • Proposed fix (what it should be)
    • Category and severity
  4. Save each report to quality_reports/:

    • For .tex files: quality_reports/FILENAME_report.md
    • For .qmd files: quality_reports/FILENAME_qmd_report.md
  5. Leave source files unchanged — fixes are applied after the user reviews the report. Only produce the report. Fixes are applied separately after user review.

  6. Present summary to the user:

    • Total issues found per file
    • Breakdown by category
    • Most critical issues highlighted

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Turn an incoming set of findings — from an AI reviewer, a referee report, a code review, a linter, or a second model — into verified fixes, without letting a confident misread damage correct work. Every finding is a CANDIDATE until checked against the actual source. Use whenever you receive review comments, audit findings, or a critique you did not write yourself, especially when the reviewer is a model or when the volume is too large to check by feel.

中文简介正在准备中。当前显示原文说明。

pedrohcgs/claude-code-my-workflow16662026年9月28日 更新

Enforce the replication-protocol.md rule by cross-checking numeric claims in a manuscript against the actual R / Stata / Python outputs. Report PASS/FAIL per claim against tolerance thresholds. Use before submission and before releasing a replication package.

中文简介正在准备中。当前显示原文说明。

pedrohcgs/claude-code-my-workflow16662026年9月28日 更新

Before and after changing anything shared — a function's return value, a signature, a schema, a label set, a config default, a constant, a file format — find every consumer and actually run them. Catches the change that looks purely additive but silently breaks a contract in a file you never opened. Use when editing shared code, adding a field/column/return element, renaming, changing units or defaults, or touching a pipeline that produces reported numbers.

中文简介正在准备中。当前显示原文说明。

pedrohcgs/claude-code-my-workflow16662026年9月28日 更新

Snapshot the computational environment for a replication package — detects the analysis stack (R / Stata / Python) and emits the right lockfiles (renv.lock + sessionInfo.txt, requirements.txt / environment.yml / uv.lock, Stata version + ado package list), records seeds and RNG kind, optionally writes a pinning Dockerfile, and produces a paste-ready "Computational requirements" block. Use when user says "capture the environment", "snapshot my dependencies", "pin the versions", "make a renv.lock / requirements.txt", "make this byte-reproducible", or before releasing a replication package to openICPSR / the AEA Data Editor.

中文简介正在准备中。当前显示原文说明。

pedrohcgs/claude-code-my-workflow16662026年9月28日 更新

challenge

免费

Stress-test a finding against the choices you did not make. Enumerates the discrete forks a competent analyst could have taken (measure definition, sample filter, control set, clustering level, weighting, functional form), runs the specification grid, and reports the distribution rather than a point estimate — then attacks the identifying assumption with named, computable sensitivity statistics. Use when the user says "is this robust", "challenge this result", "specification curve", "multiverse", "how sensitive is this", "what if I'd used a different measure", "stress-test my estimate", or before a result becomes a headline claim. NOT a reviewer of prose or code — it challenges the CLAIM.

中文简介正在准备中。当前显示原文说明。

pedrohcgs/claude-code-my-workflow16662026年9月28日 更新

Save a structured state snapshot before stopping or handing off. Captures the active plan, recent decisions, file pointers (with line numbers), open questions, and the next 1–3 actions into a checkpoint file under `quality_reports/checkpoints/`. Optionally proposes `[LEARN]` entries to add to MEMORY.md. Use when user says "checkpoint", "save state", "snapshot before I stop", "where am I", "wrap up the session for handoff", or before a long break / model switch / collaborator handoff. Companion to (NOT replacement for) the narrative session-log workflow.

中文简介正在准备中。当前显示原文说明。

pedrohcgs/claude-code-my-workflow16662026年9月28日 更新

查看 pedrohcgs 的全部技能

报告此技能的问题