jamestexas
- 32 skills
- 0 followers
- 6 hours ago last updated
- ▌ Survey · jamestexasMulti-perspective codebase survey that produces beads and mermaid diagrams from code structure. Each agent perspective (prod, staging, dev, feature, PM) examines the same codebase at a different zoom level, creating tagged beads and a disagreement matrix.
- ▌ Handoff · jamestexasCompact a session into a handoff at the work SEAM — where this session ends and the next resumes. Writes a rosary mailbox entry, bead comment, jj checkpoint, and /tmp view; `--resume` drains it next session. Use at the end of a task another session must continue, or to resume one — not a general summary.
- ▌ Pr Board · jamestexasAnswers "how are my PRs?", "did I address the review?", "anything waiting on me?". Lectio-first via authored-PR activity (reviews/comments by others, excluding your own replies), falls back to gh for coverage gaps, joins to local worktrees, prints a board of what needs you. Read-only.
- ▌ Pr Review · jamestexasGive or respond to PR reviews with structural awareness via mache. Review mode: review-prep diagrams + impact analysis, parallel analysis agents, one consolidated GitHub review. Respond mode: address reviewer comments.
- ▌ Doc Triage · jamestexasFind internal docs (not for external consumers), review against code reality, bead real items, archive stale files. Converts markdown debt into tracked beads.
- ▌ Self Audit · jamestexasPre-review self-audit of a PR branch: dead struct fields, rotting comments, duplicate types, scope drift — what a human catches but a compiler won't — then dispatches an adversarial agent for deeper design flaws. Use before tagging a reviewer, or after a self-directed refactor.
- ▌ Work Scope · jamestexasDecompose feature work into reviewable, shippable PR-sized units before coding starts. Use for a ticket, a feature description, or before a multi-file change. Feeds writing-plans — each unit becomes a plan.
- ▌ Break Glass · jamestexasEmergency IAM elevation for oncall/debugging. Discovers GCP projects and guides through granting/revoking permissions.
- ▌ Mache Usage · jamestexasStart or locate a running mache MCP server for a source path or .db file. Builds a .db from source if needed. Base skill used by diagram-gen-spec, diagram-gen-emergent, and review-prep. Returns port and session ID.
- ▌ Review Prep · jamestexasSynthesize a PR's spec-driven diagram, emergent diagram, and impact analysis into reviewer context: what's proposed vs. what the code does vs. blast radius of changed symbols. Local only, never posted to GitHub.
- ▌ Claim Ledger · jamestexasBefore opening a PR, enumerate every behavior it claims — stated, callers- unaffected, invariants-preserved — and tag each with the strongest evidence actually held: RAN, READ, or ASSUMED with a closed-set reason. Ship the ASSUMED residue in the PR description; log harness blockers durably. After review, reconcile each correctness comment against the ledger so misses are classified as harness / context / attention / lying-test with data, not vibes. Use when peers keep finding correctness bugs you didn't, when the test harness is too hard to run so you read instead, or in a monorepo where blast radius exceeds what one head holds.
- ▌ Explain Work · jamestexasReview a PR, ticket, or path and explain it so it sticks — mache/CODEOWNERS/ ticket context synthesized into a taught explanation, not a bare findings list. Own work gets onboarding framing; a peer's gets findings-teaching. Not for posting reviews (pr-review) or the reviewer-only pre-flight alone (review-prep). Local only.
- ▌ Feature Impl · jamestexasResearch-first feature implementation workflow. Use when building new features or net-new code that should follow existing codebase patterns. Enforces pattern discovery before coding; dispatches to repo-specific standards skills for convention checks.
- ▌ Review Queue · jamestexasFan out isolated, one-per-PR reviews across your queue (own context + worktree per PR, no cross-pollution), then synthesize one report. Pulls the queue from a review inbox (zen) or gh; posts nothing without per-PR authorization.
- ▌ Pr Review Kit · jamestexasSelf-contained playbook for rigorous PR review: state inspection, design-intent hunting, verification rules (cite sources, walk commits, verify artifacts), agent dispatch, falsifiable-matrix output, GitHub posting only with explicit authorization. Generic, sequential phases.
- ▌ Test Fidelity · jamestexasHunt vacuous / low-fidelity tests — the ones that pass whether or not the code is wrong in the way they claim to catch. Probes four shapes: a double that dodges the real thing, an assertion too loose to constrain behavior, inputs that never reach the claim, and coverage that is claimed but not guaranteed. Uses mache/modmap for value-origin and branch-reachability evidence and dispatches an adversarial agent for judgment. Use on a test-bearing PR or diff before review, or when a suite "passes" but you don't trust it.
- ▌ Workflow Audit · jamestexasMine the user's Claude Code chat corpus for self-optimization patterns — repeated corrections, tool thrash, dropped threads — into a ranked, PII-scrubbed report. Different from self-audit (PR code review). Dispatch as a sub-agent to keep context clean.
- ▌ Diagram Gen Spec · jamestexasGenerate a top-down diagram of intended architecture from a mache schema file — what the PR proposes, not what the code does. Local reviewer context only; pair with diagram-gen-emergent for spec-vs-reality drift.
- ▌ First Party Audit · jamestexasBefore writing glue, a wrapper, or a "small helper", audit whether the capability already exists first-party — in the binary, the codebase, or the platform — and whether existing glue bypasses a better first-party implementation. Use when adding shell/Taskfile/CI glue, when a helper feels trivially writable, or when the same logic seems to exist twice. Produces an inventory with receipts, not vibes.
- ▌ Repo Homepage Set · jamestexasAudit and set the GitHub repo homepage URL — the link on the repo card's "About" panel and every search result. Detects candidates from docs sites, registries, and demos; applies via gh repo edit after approval. Sub-skill of repo-seo-curator.
- ▌ Repo Topic Tagger · jamestexasAudit and apply GitHub topic tags for discoverability — proposes tags from code signals, deduplicates against current tags, applies via gh api after explicit approval. Sub-skill of repo-seo-curator.
- ▌ Problem Decomposer · jamestexas bundleDecompose an aspiration into dispatchable bead specs via 5-whys descent + a 7-property rubric. Use when starting new platform/capability/migration work that needs breaking down before agents can ship it, or to audit a backlog for orphan-dispatchable beads.
- ▌ Readme Restructure · jamestexasRestructure a README for human skimmers and LLM ingestion — fixes frontloaded internals, moves the value prop into the first 200 tokens, generates a diff for review. Preserves content, reorders disclosure. Sub-skill of repo-seo-curator.
- ▌ Taskfile CI Parity · jamestexasWire validation so local == CI by construction: every check is a Taskfile target; CI and hooks invoke it rather than reimplementing it. Use when adding a validation gate, when local/CI disagree, or when a hook duplicates a command.
- ▌ Repo Social Preview · jamestexasAudit the GitHub OpenGraph social preview image shown when a repo URL is posted on HN/Twitter/Slack/Discord. Flags if missing, checks clarity at small sizes, suggests sources, reports manual upload steps. Sub-skill of repo-seo-curator.
- ▌ Counterfactual Audit · jamestexasUse when asked whether a repo's architecture is still right — a counterfactual "how would this be designed today?" question, a suspicion of over/under-engineering or monolith-vs-split, recurring bug families that smell structural, or before committing to a major refactor. Read-only, evidence-first, multi-pass; "the current design is largely right" is a valid verdict. Works on any language/repo.
- ▌ Diagram Gen Emergent · jamestexasGenerate a bottom-up diagram of actual code coupling from cross-references — what the code does, not what was intended. Use for structural PR review; pair with diagram-gen-spec for intended-vs-actual drift.
- ▌ Structural Pr Review · jamestexasDeterministic PR-review chain with pluggable structural intelligence. Fetches the PR into an isolated worktree, runs blast-radius/impact analysis through whatever code-intelligence tool is available (a depgraph tool like modmap, or an MCP server like mache), applies the pr-review-kit discipline, teaches the result via explain-work, drills confirmed findings to method granularity, and emits a falsifiable matrix. Posts to GitHub only on explicit authorization; degrades gracefully when no structural tool is present. Use to review a peer's PR (or your own) with structure-aware rigor and a reproducible sequence.
- ▌ Contract Parity Audit · jamestexasUse when one interface/trait has multiple implementations that are assumed equivalent (storage backends, providers, transports), when several public surfaces (CLI/API/webhook/worker) expose the same verb, when bugs cluster as "works on X but not Y", or to scope a guardrail-parity fix before estimating it. Read-only behavioral-contract audit producing two matrices; narrower and cheaper than a full counterfactual-audit — often its follow-up.
- ▌ Prior Art Cartographer · jamestexas bundleProduce cited, structured comparisons between a project and external systems solving adjacent problems; updates a prior-art matrix. Use for prior-art research or "are we reinventing X?" before committing to a design. Max 5 systems/invocation; no uncited claims.
- ▌ Repo Description Polish · jamestexasAudit and polish the GitHub repo description — the pitch shown in search results, previews, and embeds. Proposes a stronger one from README + signals; applies via gh repo edit after approval. Sub-skill of repo-seo-curator.
- ▌ Linear Escalation Triage · jamestexasUse for Linear tickets assigned to you — oncall queue sweeps, aged P1/P2 escalations in Triage > 7 days, stale Todos needing cleanup, or an external escalation (Slack/support) surfacing a ticket needing a triaged reply.