yangshu2087/repo-postcheck-summary
.agents/skills/repo-postcheck-summary/SKILL.md
Run the minimum useful verification after repository bootstrap or small setup changes, then produce a concise change summary. Use when a repo has just been initialized or had Codex scaffolding added and the user wants a quick verification-and-summary pass.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add yangshu2087/Codex repo-postcheck-summaryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 3:36 PM35.4s1 file scanned
SKILL.md
- name:
- repo-postcheck-summary
- description:
- Run the minimum useful verification after repository bootstrap or small setup changes, then produce a concise change summary. Use when a repo has just been initialized or had Codex scaffolding added and the user wants a quick verification-and-summary pass.
Repo Postcheck Summary
Use this skill after repository bootstrap, setup-file changes, or other small structural edits where a full test suite would be excessive.
Workflow
- Run the smallest checks that prove the setup is coherent:
git status --short- inspect the changed files
- one repo-specific validation command if the repo guidance calls for it
- Do not invent heavyweight validation for a minimal repository.
- Summarize changes in three parts:
- what files were added or changed
- what was verified
- what remains unverified
- If the repo has no meaningful test or build surface yet, say that explicitly instead of pretending validation was comprehensive.
- If the repo is about Git behavior, prefer replaying the exact Git commands relevant to the scenario over generic tooling.
Output standard
- Keep the summary short and operational.
- Include exact repo path.
- Include exact verification commands run.
- Call out any remaining risk in one sentence.
Related Skills
yangshu2087/terrashark
development
VerifiedTrustedCommunity
Use when explicitly reviewing, generating, refactoring, or migrating Terraform/OpenTofu IaC and checking failure modes such as identity churn, secrets, blast radius, CI drift, or compliance gates.
SKILL.mdUpdated Apr 16, 2026
yangshu2087/stitch-ui-prompt-architect
development
VerifiedTrustedCommunity
Use when the user explicitly mentions Google Stitch and wants a structured Stitch-ready UI prompt or prompt refinement from rough product/design ideas.
SKILL.mdUpdated Apr 16, 2026
yangshu2087/stitch-react-components
development
VerifiedTrustedCommunity
Use when the user explicitly mentions Google Stitch and asks to convert Stitch designs into Vite, CRA, or generic React components.
SKILL.mdUpdated Apr 16, 2026
yangshu2087/stitch-nextjs-components
development
VerifiedTrustedCommunity
Use when the user explicitly mentions Google Stitch and asks to convert Stitch designs into Next.js App Router components.
SKILL.mdUpdated Apr 16, 2026