All authors
Claude Skills by renzrollon
github.com/renzrollon24 skills0 installs29 views
- BootstrapOnboard a brownfield project into OpenSpec — analyze the existing codebase with parallel explorer agents, write an initial architecture document, then generate one spec per discovered feature describing what is already built. Use when adopting spec-driven development on a repo that has code but no specs.Votes: 0GitHub stars: 17
- CommitCreate a single feature-level commit after a change is implemented. Reads the OpenSpec change artifacts to write a verb-phrase conventional-commit message with an outcome summary and optional issue reference. Commit only — never runs tests, typecheck, lint or build, and never pushes.Votes: 0GitHub stars: 17
- DispatchRoute a request to the right interlock skill, after one batched pre-flight that loads git state, OpenSpec status, open tasks and graph presence in a single pass. Use when you are not sure which skill applies, or at the start of a session to orient before doing anything else.Votes: 0GitHub stars: 17
- Docs DigestCompress a repo's docs and OpenSpec specs into one token-dense, agent-only primer at .claude/graph/DOCS_DIGEST.md — the prose twin of GRAPH_REPORT.md. Use when docs context is too large to load, after substantial docs or spec edits, or when asked to rebuild or refresh the docs digest. Not for producing human-readable documentation.Votes: 0GitHub stars: 17
- EvalsAuthor an Interlock eval case from an observed model-behaviour failure, and read a completed eval results run. Use when you have a reproduced failure — an archived proposal, a changelog entry, a run artifact, or a transcript — worth regression-testing against a real model, or when an eval run has finished and you need to know whether it is a regression, run-to-run variance, or no signal. Authoring needs cited evidence; the verdict comes from `interlock evals triage`, never from your own reading.Votes: 0GitHub stars: 17
- Explain CodeExplain code to a beginner in that stack — either a module walkthrough (what each function does, how calls link, where data flows, which patterns recur) or a commit teach-in (why each file changed, what changed, blast radius, what would break if it were left out). Use when asked to explain code, walk through a directory, or explain the last commit.Votes: 0GitHub stars: 17
- ExploreDeep codebase reconnaissance with parallel read-only investigators — fans out automatically when a question spans multiple subsystems, options, or cross-cutting concerns, then synthesizes one coherent picture. Use before designing a change, when tracing how something works end to end, or when you need to know the blast radius of touching a shared value.Votes: 0GitHub stars: 17
- Fix TestsDiscover and persist how a project's tests run, then run the suite and repair failures by root cause — clustering failures by error signature, fixing the shared cause once, and asserting no test was weakened. Use when tests are failing, the suite is red, CI pasted a failure log, or someone asks to make the tests pass.Votes: 0GitHub stars: 17
- GraphBuild and query a local, deterministic codebase knowledge graph (imports, symbols, OpenSpec specs, memory) so agents navigate with token-budgeted subgraphs instead of re-grepping. Use when indexing a repo, finding who consumes a symbol, tracing how one module reaches another, or before a deep explore or review sweep.Votes: 0GitHub stars: 17
- Manual Test PlanProduce an expert-QA manual UI test plan from an OpenSpec change plus a git commit range — every touched file accounted for, spec scenarios and tasks mapped to numbered test cases, and non-UI-testable changes flagged rather than dropped. Use when asked for a manual test plan, QA checklist, or UI verification plan after implementing and before opening an MR.Votes: 0GitHub stars: 17
- MrGenerate a merge-request or pull-request summary from the change artifacts and diff, then create or update it on whichever platform the remote points at — GitLab via glab, GitHub via gh. Optional comment-only add-ons post the manual test plan or a teaching walkthrough. Use when opening an MR/PR, refreshing its description, or attaching a test plan.Votes: 0GitHub stars: 17
- ReportRead the indicator report over Interlock's three recorded corpora — outcome records, run trajectories, review metrics — and say what it does and does not license. Use when someone asks how the loop is actually performing, whether continuity is working, how often review findings survive, which gate blocks most, or whether there is yet enough evidence to change a cap or a gate. The figures come from `interlock report`, never from your own counting; the judgement you add is about denominators, n...Votes: 0GitHub stars: 17
- Review CodeAdversarially verified multi-dimensional review of a code diff. Runs independent reviewers across language, architecture, QA, devops, security and technical-lead, then makes two skeptics try to refute every blocker and warning before it reaches you. Use after implementing a change, before opening an MR, or when a diff is high-stakes enough that false positives would waste real time.Votes: 0GitHub stars: 17
- ShipLaunch the Interlock ship workflow — take a reviewed OpenSpec change from tasks to commit in one uninterrupted run (waves, verify, commit). Default is lean; pass --strict for review, handoff and conformance. Use when the user ran /interlock:ship, asked to ship a reviewed change, or spec --continue passed the readiness gate. Never invoke after spec unless they asked.Votes: 0GitHub stars: 17
- Review ArtifactsReview OpenSpec change artifacts before anyone writes code — architecture quality and design completeness, then spec completeness and testability. Catches a wrong idea at the cheapest possible moment. Use after generating proposal, design, tasks and delta specs, and before implementing.Votes: 0GitHub stars: 16
- SpecTake a rough intent to a reviewed, implementation-ready OpenSpec change — explore first, generate proposal, design, tasks and delta specs via the OpenSpec CLI, then gate them through an artifact review. Stops at the human checkpoint, having written nothing but specs. Use when starting a new feature, refactor, or bug fix.Votes: 0GitHub stars: 16
- Bump ReleaseBump the project's version in every manifest at once, then commit, tag, push, and cut a release, so no manifest keeps a stale version.Votes: 0GitHub stars: 7
- ExploreDeep read-only reconnaissance before a change is designed. Fans out parallel investigators when a question spans several subsystems, compares options, needs cross-file tracing, or changes what a shared value means, then synthesizes one picture and, in an autonomous run, writes a durable brief. Use when asked how something works end to end, what breaks if a shared value changes, which of several approaches fits, or to explore, map, trace, or investigate before building. Skips single-file quest...Votes: 0GitHub stars: 7
- Fix TestsDiscover and persist how a project's tests run, then run the suite and repair failures by root cause, clustering failures by error signature, fixing the shared cause once, and asserting no test was weakened. Use when tests are failing, the suite is red, CI pasted a failure log, or someone asks to make the tests pass. Not a general debugger, and not for a failure that is not a test run.Votes: 0GitHub stars: 7
- Readme PitchRewrite this repository's README into a first-screen pitch. Hero above the fold, pitch done before the first heading, technical detail moved into docs with links, every test pin and anchor kept.Votes: 0GitHub stars: 7
- Product SpineHelp an engineer act as product owner: suggest parallel work threads (features, improvements, fixes) from the repo, then draft, review, and capability-check the one-pager, epics, and briefs that land them. Writes artefacts, never code. Answers "can the platform do X?" from the project's own primer.Votes: 0GitHub stars: 7
- Session HandoffSave where this session stands to a handoff file before a context reset, so the next session or agent resumes without re-deriving decisions. Lists stranded work, redacts secrets, and proposes reusable rules for your instruction file.Votes: 0GitHub stars: 7
- Session PrimerBrief a fresh session in one read-only pass, from git state, open plan checkboxes, the newest handoff file, and the instruction file. Use at session start or when the user says "where was I", "catch me up", "continue where we left off", "what's the state of this repo", or "brief me". Does not trigger on a question that names a specific file or feature, and never edits anything.Votes: 0GitHub stars: 7
- Session RetroRetro the current session. Score it against session shapes, flag token waste with next-turn fixes, and propose wire-ins into the skills this conversation actually called.Votes: 0GitHub stars: 7