all publishers

cwijayasundara

@cwijayasundara source repo

122 published skills · page 2 of 2

  1. ▌
    Fastapi Code · cwijayasundara bundle
    Build FastAPI backends — dependency injection with Depends(), Pydantic v2 request/response validation, async vs sync route rules, background tasks, and testing with TestClient. Use for any FastAPI route, dependency, or Pydantic model. Not for database/ORM design (no SQLAlchemy content here) or non-FastAPI Python web frameworks. Triggers on "FastAPI route", "Depends()", "Pydantic model", "FastAPI dependency", "FastAPI testing", "TestClient", "async def vs def FastAPI".
    6 repo stars
  2. ▌
    Langchain Code · cwijayasundara bundle
    Build LangChain agents in Python — create_agent, chat model initialization, tool binding, structured output, and middleware. Use for a single-agent tool-calling loop with a system prompt and a fixed tool list; use langgraph-code instead when the task needs explicit multi-step state-machine control flow, and deepagents-code instead when it needs a pre-assembled filesystem/planning/subagent harness for long-running work. Triggers on "LangChain agent", "create_agent", "chat model", "tool calling agent", "structured output langchain", "bind_tools".
    6 repo stars
  3. ▌
    Langgraph Code · cwijayasundara bundle
    Build stateful, multi-actor LangGraph agents in Python — StateGraph definition, conditional routing, checkpointing/persistence, and human-in-the-loop interrupts. Use when a task needs explicit multi-step control flow, crash/interrupt recovery, or approval gates — not for a single-turn prompt or a simple tool-calling loop (use langchain-code's create_agent for that). Triggers on "LangGraph", "state graph", "stateful agent", "multi-step agent workflow", "checkpointing", "resume from crash", "human in the loop agent".
    6 repo stars
  4. ▌
    Agent Readiness · cwijayasundara
    Show how mature/safe this codebase is for heavy AI-agent use — a synthesis dashboard across 8 pillars, aggregating signals the harness already collects. Read-only report; aggregates state already on disk.
    6 repo stars
  5. ▌
    Deepagents Code · cwijayasundara bundle
    Build long-running, production-ready agents with DeepAgents — the opinionated harness on top of LangGraph/LangChain providing filesystem access, task planning, subagent delegation, and context management out of the box. Use for long-running coding/research/multi-step tasks where you'd otherwise hand-assemble that middleware stack yourself; use langchain-code's plain create_agent instead for a simple single-tool-call loop with no need for planning or filesystem access. Triggers on "DeepAgents", "create_deep_agent", "agent harness", "long-running agent", "coding agent with filesystem", "subagent spawning".
    6 repo stars
  6. ▌
    Tracker Publish · cwijayasundara bundle
    Publish approved Claude Harness dependency groups to Linear/Jira-compatible tracker tasks and write the local tracker mapping contract.
    6 repo stars
  7. ▌
    Portfolio Rollup · cwijayasundara
    Aggregate per-repo compliance attestations into one integrity-hashed portfolio rollup — verifying each attestation's sha256 integrity, recording an unattested repo as a compliance gap, and computing harness-version drift across the fleet. Use over a local collection directory of attestations, or with --fetch to gather them via fleet.json + gh api. --verify re-checks a stored rollup's own integrity.
    6 repo stars
  8. ▌
    Reuse Or Justify · cwijayasundara
    Use when reuse-scout fires at intake (band ≥ medium, a touched constitution invariant, or a same-release clone cluster) — run the confidence-gated reuse-vs-new dialogue and record the decision + performance budget before code. [Internal discipline — invoked by /change, /feature, and /sprint intake; direct use is a power-user path.]
    6 repo stars
  9. ▌
    Scaffold Upgrade · cwijayasundara
    Upgrade harness control-plane files (hooks, scripts, git-hooks, agents) in a previously scaffolded project without wiping project-manifest or state. Dry-run by default.
    6 repo stars
  10. ▌
    Mockup · cwijayasundara
    Create a UI mockup, component, or page as a disposable artifact. No SDLC pipeline, no evaluator, no security review.
    6 repo stars
  11. ▌
    Fix From Diagnostics · cwijayasundara
    [Internal pipeline stage — run by /auto self-heal and /implement validation when lint/type error volume is high; invoke directly only as a power user.] Turn compiler/linter output into a sharded work queue; fix per package with optional adversarial review — no full monorepo suite mid-shard.
    6 repo stars
  12. ▌
    Author Prompt Surface · cwijayasundara
    Use when creating or editing .claude/agents/*.md, .claude/skills/*/SKILL.md, or .claude/commands/* — apply docs/prompting-standards.md (trigger conditions, model-agnostic bodies, no reasoning-as-text, effort floors).
    6 repo stars
  13. ▌
    Pinning Down Behavior · cwijayasundara
    Use when checking-coverage-before-change reports an UNCOVERED symbol you must edit — writes characterization (pin-down) tests at the nearest observable seam and verifies they bite before any production edit. [Internal discipline — applied automatically by pipeline agents mid-task; direct use is a power-user path.]
    6 repo stars
  14. ▌
    Arch Doc · cwijayasundara
    Author a standalone architecture / ARB (Architecture Review Board) narrative document. Disposable artifact — no SDLC pipeline, no planner/generator/evaluator, no schemas or mockups.
    6 repo stars
  15. ▌
    Research · cwijayasundara
    Produce a research / analysis / deep-dive report as a disposable artifact. No SDLC pipeline, no evaluator, no security review.
    6 repo stars
  16. ▌
    Keeping Refactors Pure · cwijayasundara
    Use when committing any change that includes structural work (rename, move, extract, reorder) in an existing codebase — keeps refactor commits behavior-free and behavior commits refactor-free so regressions stay attributable. [Internal discipline — applied automatically by pipeline agents mid-task; direct use is a power-user path.]
    6 repo stars
  17. ▌
    Upgrading Dependencies · cwijayasundara
    Use when bumping a dependency version — package.json, pyproject.toml, requirements, or lockfile changes — in an existing codebase. Classifies the bump, audits the usage surface from the code graph, and isolates the upgrade in its own proven commit.
    6 repo stars
  18. ▌
    Install Framework Packs · cwijayasundara
    [Internal pipeline stage — run by /scaffold; invoke directly only as a power user.] Verify agent-framework skill packs declared in project-manifest.json#framework_skill_packs and print normal-terminal install commands for missing packs. Use after /scaffold reports PENDING MANUAL INSTALL, after manually adding a pack to the manifest, or to verify all configured packs are present.
    6 repo stars
  19. ▌
    Checking Migration Safety · cwijayasundara
    Use when a planned change touches persisted data shape — ORM models, migration files, schema definitions, serialized formats, or message contracts — in /change, /refactor, or /implement on an existing codebase. Routes schema changes through expand-contract and proves reversibility before any deploy. [Internal discipline — applied automatically by pipeline agents mid-task; direct use is a power-user path.]
    6 repo stars
  20. ▌
    Sprouting Instead Of Editing · cwijayasundara
    Use when a symbol that must change is UNCOVERED and unpinnable (seam score < 0.5, or a skeletons/-flagged god file with no clean boundary) — adds behavior in a new fully-tested unit instead of editing legacy code in place. [Internal discipline — applied automatically by pipeline agents mid-task; direct use is a power-user path.]
    6 repo stars
  21. ▌
    Writing Acceptance Tests First · cwijayasundara
    Use when a story is about to move from acceptance criteria to implementation — in /test's plan-phase deliverable or /change Step S4, before any production code is written — to write a business-readable acceptance test against a Ports-and-Adapters seam with a test-double adapter, and confirm it fails for the right reason before implementation proceeds. [Internal discipline — applied automatically by pipeline agents mid-task; direct use is a power-user path.]
    6 repo stars
  22. ▌
    Checking Coverage Before Change · cwijayasundara
    Use when about to edit any existing (non-greenfield) symbol — before the first Edit/Write to production code in /refactor, /change, or /vibe — to learn which tests cover it and route uncovered code to pinning or sprouting. [Internal discipline — applied automatically by pipeline agents mid-task; direct use is a power-user path.]
    6 repo stars