Skip to content

Add Claude Code skills for LIF Core (dev loop, PR lifecycle, ops, planning)#992

Open
bjagg wants to merge 4 commits into
LIF-Initiative:mainfrom
bjagg:add-claude-skills
Open

Add Claude Code skills for LIF Core (dev loop, PR lifecycle, ops, planning)#992
bjagg wants to merge 4 commits into
LIF-Initiative:mainfrom
bjagg:add-claude-skills

Conversation

@bjagg

@bjagg bjagg commented Jun 18, 2026

Copy link
Copy Markdown
Contributor
Description of Change

Adds 10 Claude Code skills under .claude/skills/ (alongside the existing docs-index skill), each encoding a recurring LIF-Core workflow as an executable, convention-aware procedure so they run consistently instead of being re-derived ad hoc each time.

  • What problem it solves: multi-step workflows (PR lifecycle, ops deploys, planning, issue triage, testing) were done from memory each session, which led to convention misses and rework. These capture the workflow and the real LIF-Core footguns (e.g. the 3-Dagster-pyproject rule, fail-closed tenant routing, single-uvicorn-worker async, append-don't-force-push, "only CLAUDE.md auto-loads").
  • The skills:
    • Dev loop: test (ruff/ty/pytest/poly + integration + vitest), refactor (atomic-change→verify), adr-write (per-domain-folder ADR layout)
    • PR lifecycle: self-review-relay (multi-lens pre-review pass), open-pr (reads AGENTS.md/CONTRIBUTING.md/template, base-branch + fork checks), address-pr-feedback (triage + reply + re-request)
    • Ops / scale: new-microservice (the add-a-service runbook), promote-to-demo (dev→demo gated promotion), multi-agent-plan (sequential design passes), issue-sweep (multi-agent stale-issue audit)
  • Side effects / limitations: docs-only — Markdown skill files + 4 added cspell.json words. No application code, runtime, or deployment config is touched. multi-agent-plan and issue-sweep use the Workflow tool and explain a fallback when it isn't available.
  • How to test: invoke any skill (e.g. /test, /open-pr) in a LIF-Core session; cspell passes; no code paths are affected.
Related Issues

No tracking issue — developer-experience tooling. Happy to file one if the team prefers.

Type of Change
  • Documentation update
Project Area(s) Affected
  • Documentation (docs/, READMEs, ARCHITECTURE.md, CLAUDE.md) — specifically .claude/skills/
Checklist
  • code passes linting checks (uv run ruff check) — N/A to Markdown; pre-commit ran clean on every commit
  • pre-commit hooks have been run successfully (cspell passed on each commit)
  • documentation is changed or added
Testing
  • Manual testing performed — cspell clean; skill frontmatter/structure verified
Additional Notes
  • Adapted from a sibling repo's skill set, re-lensed for LIF-Core's stack (Python/Polylith + FastAPI + React/TS) rather than copied.
  • Deliberately not ported: a custom code-review skill (LIF-Core already has built-in /code-review + /security-review), plus session-wrapup and several domain-specific skills that don't apply here.

bjagg and others added 4 commits June 8, 2026 14:32
Port four agent skills from tabletop-platform, re-lensed for LIF Core's
stack (Python Polylith + FastAPI + React/TS frontends):

- test: full check suite (ruff/ty/pytest/poly + integration + advisor-app vitest)
- refactor: atomic-change-then-verify loop with uv-based verify gate
- adr-write: knows the per-domain-folder, per-folder-numbered ADR layout
- multi-agent-plan: Workflow of sequential Opus Plan agents, 4 lenses
  (FP/Polylith -> backend correctness -> frontend/holistic)

Skipped tabletop's code-review skill (lif-core already has built-in
/code-review + /security-review) and session-wrapup (wrapper-level concern).

cspell: add "elif" and "threadpool" to the word list.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Three more agent skills for LIF Core operations:

- new-microservice: executable form of the adding-a-new-microservice
  runbook (base + project + auth + compose + CI + CFN + tests), with the
  trimmed-deps / PEP440 / per-project-pyproject / brick-match pitfalls baked in.
- promote-to-demo: dev -> demo promotion (release-demo.sh tag bump ->
  aws-deploy.sh stacks -> MDR frontend -> SAM-if-needed), gated on dev
  validation + explicit sign-off; sequential-deploy + reset-DB guards.
- issue-sweep: GitHub-issue analogue of a backlog-drift sweep. Workflow
  fans out cheap judges per open issue (resolved-by-merged-code?), arbitrates
  disagreements, surfaces an evidence-backed close-list; never auto-closes.

cspell: add "oneline" to the word list.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ress-pr-feedback)

Three skills matching the observed PR workflow in this repo:

- self-review-relay: Workflow of 3 parallel review lenses (correctness/
  security, robustness/ops, tests/conventions/scope) + a synthesis pass that
  sorts blockers vs nits. The rigor step before requesting review.
- open-pr: scaffolds a convention-compliant PR. Encodes the gotcha that only
  CLAUDE.md auto-loads -- AGENTS.md + CONTRIBUTING.md + the PR template must be
  read each time. Fills the template, enforces Issue #XXX commits + green
  pre-commit + one-issue-per-PR + no-self-approve.
- address-pr-feedback: triage reviews + inline comments, fix/clarify/push-back/
  defer, append commits (never force-push per feedback_pr_commit_style), reply
  inline, re-request review. Outward-facing replies gated on confirmation.

cspell: add "aget" (LangGraph async method prefix).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Dry-run findings: passing the issue list via the Workflow args field arrives
undefined (pipeline() throws). Inline the Phase-1 list as a const instead.
Also document the cost (~75K tokens/issue) and default to a label filter or
stalest-N rather than sweeping all open issues.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant