OnourImpram/claude-code-for-social-scientists / .claude/skills/repo-release-integrity-check
repo-release-integrity-check
VerifiedUse before a tag, GitHub release, or Zenodo archive, when README, CATALOG, CHANGELOG, CITATION.cff, the disclosure aggregate, and skill discovery must agree, or when a go or no-go release verdict needs recorded evidence behind it.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.9 KB |
SKILL.md
View on GitHub---
name: repo-release-integrity-check
description: Use before a tag, GitHub release, or Zenodo archive, when README, CATALOG, CHANGELOG, CITATION.cff, the disclosure aggregate, and skill discovery must agree, or when a go or no-go release verdict needs recorded evidence behind it.
---
# Repo Release Integrity Check
## When to use
Use this skill before a tag, GitHub release, Zenodo archive, DOI announcement, or public repository update when metadata drift would damage citation trust. It is the last gate in the lifecycle, and it consumes ai-disclosure-auditor verdicts rather than recomputing them. It is not for packaging the open-science deposit itself, that is open-science-release-packager, and it is not for auditing author contribution statements, that is authorship-contribution-ledger.
## Inputs
- Target version.
- Release date.
- Changed booklet identifiers.
- Expected DOI state.
- GitHub release notes, if drafted.
- CI status or local validation output.
## Workflow
1. Confirm the target version and whether the change is patch, minor, or major.
2. Read the README and README.tr status blocks against the planned release facts.
3. Reconcile CATALOG counts and status rows with the booklet directories on disk.
4. Walk the CHANGELOG entry and the Zenodo DOI notes for the version being shipped.
5. Compare CITATION.cff concept DOI, version DOI, date, and version fields with the release plan.
6. Cross-reference the AI disclosure aggregate with booklet frontmatter, since this is where drift hides longest.
7. Inspect each release booklet's frontmatter for human review, citation counts, fabricated citations, disclosure standard, license, and status. This step needs judgment rather than matching.
8. When the release includes project skills, list the `.claude/skills` directories and confirm discovery matches the declared set.
9. Sweep issue templates, PR template, workflows, citation check, and secret scan status.
10. Produce release blockers and final go or no-go verdict.
## Output
Return:
- Version verdict.
- Metadata checklist.
- Booklet checklist.
- Skill checklist.
- DOI and citation checklist.
- CI and security checklist.
- Release blockers.
- Go or no-go decision.
- What to record at session end: the version checked, the blocker count and resolution status, and the go or no-go verdict with the evidence file or CI run that supports it.
## Verification
- Local validator or CI evidence is included.
- DOI claims are not marked verified unless checked against the release record.
- README, CATALOG, CHANGELOG, and AI disclosure aggregate agree.
- Release status is not assigned to unreviewed or citation-unsafe booklets.
- Branch protection and required checks are noted when they cannot be applied locally.
- Before closing: the go or no-go verdict is backed by named evidence (CI run or validator output), every blocker is assigned to a file or step, and the open-science-release-packager and authorship-contribution-ledger handoffs are flagged when the release includes a Zenodo deposit or multi-author contribution record.
## Safety
Do not create tags, push releases, alter branch protection, or edit repository settings without explicit user intent and current permission evidence. Do not publish tokens or release credentials.
## Example prompt
"Run a pre-release integrity check for v1.1.0 after adding project skills."
Expected smoke output:
- A go or no-go verdict.
- A table covering README, catalog, changelog, citation, disclosure, skills, CI, and security.
- A blocker list with exact files to fix.
## Türkçe kullanım notu
Bu beceri, yayın düğmesine basılmadan önceki son kapıdır. Sürüm numarası, katalog sayıları, değişiklik günlüğü, atıf metadatası, beyan agregatı ve beceri keşfi tek tabloda karşılaştırılır, uyuşmayan her satır engele dönüşür. Doğrulanmamış DOI iddiası doğrulanmış sayılmaz, sonuç açık bir devam ya da dur kararıdır.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide 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. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |