All authors
Claude Skills by WangChangxin0809
github.com/WangChangxin08098 skills1 installs24 views
- Consolidating NotesFold a pile of agent notes, memories or scratch files back into the repository: freeze the input, synthesize separately, diff, and route each surviving entry to a doc, a guard, a subtree CLAUDE.md, or the little that is truly personal. Use when notes contradict each other or name things that no longer exist, or when asked to clean up or compact memory.Votes: 0GitHub stars: 5
- Repo IndexQuery the repository's own graph before grepping: which modules, files and documents a symbol, an import or a Governs edge touches, and what a change would reach. Use when a question spans directories, when asked what depends on something, when grep returns hundreds of hits or none, or when someone asks for RAG, semantic search or a code index for their codebase.Votes: 0GitHub stars: 5
- Writing ChecksEnforce a convention with machinery instead of prose: PreToolUse guards that refuse an action before it runs, gates that judge the worktree in CI, selftests that prove a check can turn red, layering tests. Use when a written rule keeps being violated, when adding any lint or CI step, when asked to protect a branch or stop a destructive command, or when a check exists that nobody has seen fail.Votes: 0GitHub stars: 5
- Writing DocsWrite or restructure documentation agents and people actually read: which of the four directories it belongs in (how-to, reference, decisions, exec-plans), what belongs in a failure message instead of a file, and keeping the routing table honest. Use for any doc, runbook, README, ADR or plan; when docs are stale, contradictory or ignored; when deciding where a convention lives; when moving knowledge out of CLAUDE.md or agent memory.Votes: 0GitHub stars: 5
- Bootstrap Repo HarnessLay a repository's agent harness: CLAUDE.md, hooks, docs/, gates, guards. Use when an agent repeats a mistake or a repository has none.Votes: 0GitHub stars: 5
- Find SkillFind a Claude Code skill or plugin somebody else has already written, and judge whether to install it. Use before writing a skill for something that sounds common, when asked whether an integration exists, when looking for a plugin by capability rather than name, or before adding a skill that would duplicate one installed.Votes: 0GitHub stars: 5
- Github SurfaceWrite what GitHub itself reads: README, CONTRIBUTING, the community-health files (SECURITY, CODE_OF_CONDUCT, LICENSE, issue and PR templates) and the workflows under .github/workflows/. Use when creating or rewriting any of these, when Community Standards reports a gap, when adding or reviewing CI, or when a repository goes public. Not for docs/, which is writing-docs.Votes: 0GitHub stars: 5
- Project MemoryUse when recalling project decisions, remembering reusable discoveries, consolidating memory, or withdrawing outdated project knowledge.Votes: 0GitHub stars: 5