yarlson

52 mods across 1 repository, 3 stars between them.

coderabbit-triage

25

yarlson/yarstack

Skill Claude CodeCodex

Triage unresolved CodeRabbit feedback on the current GitHub pull request. Use for read-only disposition and, only when separately authorized, scoped remediation and remote thread closure.

3 4d ago A 39 tokens original MIT

crap-index-assess

26

yarlson/yarstack

Skill Claude CodeCodex

Assess method-level change risk with the Change Risk Anti-Patterns (CRAP) index and recommend focused testing or complexity reduction. Use when a repository configures CRAP measurement, cyclomatic complexity and automated test coverage data are available, or a user asks what CRAP means, how to calculate or interpret…

3 4d ago A 77 tokens original MIT

yarlson/yarstack

Skill Claude CodeCodex

Create one concise evidence-linked product journey record for one actor pursuing one goal. Use when product behavior needs traceable ownership, acceptance, telemetry, or service-flow documentation for a current decision or delivery gate.

3 4d ago A 46 tokens original MIT

dependency-review

28

yarlson/yarstack

Skill Claude CodeCodex

Review dependency provenance and reproducibility without modifying them. Use when manifests, lockfiles, vendor state, generated dependency state, registries, fetched tools, or version pins change.

3 4d ago A 38 tokens original MIT

docs-drift-review

29

yarlson/yarstack

Skill Claude CodeCodex

Review documentation for drift caused by the current code or configuration change. Use to identify concrete inaccuracies and, when authorized, repair only directly affected documentation.

3 4d ago A 34 tokens original MIT

docs-review

30

yarlson/yarstack

Skill Claude CodeCodex

Audit or improve general repository documentation against implemented behavior. Use for deliberate README or documentation-quality work not owned by a more specific documentation skill.

3 4d ago A 30 tokens original MIT

infra-review

31

yarlson/yarstack

Skill Claude CodeCodex

Review infrastructure-as-code and rendered deployment configuration without modifying it. Use before plan, apply, or deploy when targeting, replacement, state, availability, cost, ordering, or recovery blast radius may change.

3 4d ago A 43 tokens original MIT

jira-issue-create

32

yarlson/yarstack

Skill Claude CodeCodex

Create one or more Jira issues through acli from user-approved drafts using heading-based Context, Acceptance criteria, and Engineering notes sections. Use only when explicitly invoked to create Jira issues; use jira-issue-refine when requirements still need refinement.

3 4d ago A 53 tokens original MIT

jira-issue-deliver

33

yarlson/yarstack

Skill Claude CodeCodex

Autonomously deliver one Jira issue from intake to a ready GitHub pull request. Use only when the user authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback.

3 4d ago A 51 tokens original MIT

jira-issue-refine

34

yarlson/yarstack

Skill Claude CodeCodex

Refine one draft or existing Jira issue into a clear, evidence-backed, bounded delivery contract without implementing it. Use when creating or revising an issue before engineering handoff, especially when behavior, repository ownership, acceptance evidence, dependencies, risk, environment needs, or scope remain…

3 4d ago A 63 tokens original MIT

yarlson/yarstack

Skill Claude CodeCodex

Audit or, when authorized, rewrite persuasive product claims against shipped-product evidence. Use for landing pages, marketing-heavy READMEs, feature or pricing pages, comparisons, and calls to action.

3 4d ago A 43 tokens original MIT

phase-commit

36

yarlson/yarstack

Skill Claude CodeCodex

Create one local commit for a completed, validated, and reviewed unit of work. Use only when the user explicitly requests a commit without pushing or other delivery actions.

3 4d ago A 36 tokens original MIT

phase-implement

37

yarlson/yarstack

Skill Claude CodeCodex

Implement exactly one selected phase from an authoritative repository plan. Use when a named phase or equivalent scoped implementation unit must be completed without later-phase work.

3 4d ago A 33 tokens original MIT

phase-review

38

yarlson/yarstack

Skill Claude CodeCodex

Review one validated phase for behavior-preserving structural regressions introduced or materially worsened by the change. Use after phase validation and before final delivery.

3 4d ago A 32 tokens original MIT

phase-validate

39

yarlson/yarstack

Skill Claude CodeCodex

Validate exactly one implemented phase or scoped change against its authoritative contract. Use after implementation to re-derive criterion-level conclusions from current evidence and fix only required implementation gaps.

3 4d ago A 37 tokens original MIT

plan-create

40

yarlson/yarstack

Skill Claude CodeCodex

Create a final implementation-ready plan from a user brief, settled decisions, and repository evidence. Use when work needs ordered phases, concrete deliverables, dependencies, risks, and validation before coding.

3 4d ago A 41 tokens original MIT

plan-update

41

yarlson/yarstack

Skill Claude CodeCodex

Make the smallest evidence-backed correction to implementation-plan mechanics. Use when implementation or validation proves incorrect ordering, prerequisites, phase scope, dependencies, steps, or validation gates.

3 4d ago A 36 tokens original MIT

pr-draft

42

yarlson/yarstack

Skill Claude CodeCodex

Publish confirmed local changes as a monitored GitHub draft pull request. Use only when the user authorizes branch creation, scoped staging, commit, push, draft PR creation, and CI follow-up.

3 4d ago A 43 tokens original MIT

yarlson/yarstack

Skill Claude CodeCodex

Create, update, or consolidate adopted current-state documentation under docs/context/. Use for durable implemented architecture, ownership, runtime, domain, flow, terminology, or engineering-practice context.

3 4d ago A 40 tokens original MIT

yarlson/yarstack

Skill Claude CodeCodex

Review cross-cutting operational readiness after implementation and before deployment. Use when a concrete change may alter runtime prerequisites, failure visibility, deployment order, rollback, recovery, or production failure modes.

3 4d ago A 43 tokens original MIT

security-review

45

yarlson/yarstack

Skill Claude CodeCodex

Review a focused trust-boundary or exploit-path change without modifying it. Use when work introduces or materially changes untrusted input, privilege decisions, secret flow, dangerous sinks, or agent and tool capabilities.

3 4d ago A 43 tokens original MIT

spec-update

46

yarlson/yarstack

Skill Claude CodeCodex

Make a minimal evidence-backed update to a non-plan product, architecture, API, schema, or behavior contract. Use when implementation or validation cannot determine correctness from the current authoritative contract.

3 4d ago A 39 tokens original MIT

system-investigate

47

yarlson/yarstack

Skill Claude CodeCodex

Investigate an underdefined product, codebase, architecture, integration, or operational question through read-only repository tracing, bounded runtime evidence, and current public research. Use when the user wants to validate suspected behavior, explain why it occurs, compare plausible designs, or recommend the…

3 4d ago A 66 tokens original MIT

technical-spike

48

yarlson/yarstack

Skill Claude CodeCodex

Resolve one correctness-blocking external or version-specific technical uncertainty through bounded investigation. Use when cheap local inspection cannot establish framework, library, tool, runtime, protocol, or platform behavior needed by the current task.

3 4d ago A 45 tokens original MIT