record-session — community record-session, mytrellis, community, ide skills

v1.0.0

About this Skill

Ideal for Development Agents requiring structured session recording and analysis after commit. Method 1: Simple parameters

TbK0ng TbK0ng
[0]
[0]
Updated: 2/24/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
42
Canonical Locale
en
Detected Body Locale
en

Ideal for Development Agents requiring structured session recording and analysis after commit. Method 1: Simple parameters

Core Value

Empowers agents to generate concrete actions aligned with objectives, utilizing user requests and repository context, and providing a structured approach to session recording after commit, leveraging pre_checks and post_checks for verification and follow-up.

Ideal Agent Persona

Ideal for Development Agents requiring structured session recording and analysis after commit.

Capabilities Granted for record-session

Automating session recording after commit
Generating summaries of user requests and repository context
Debugging issues through post_checks and follow-up items

! Prerequisites & Limits

  • Requires prerequisites to be confirmed before acting
  • Must be used after human analysis
  • Limited to post_commit phase

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is record-session?

Ideal for Development Agents requiring structured session recording and analysis after commit. Method 1: Simple parameters

How do I install record-session?

Run the command: npx killer-skills add TbK0ng/mytrellis/record-session. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for record-session?

Key use cases include: Automating session recording after commit, Generating summaries of user requests and repository context, Debugging issues through post_checks and follow-up items.

Which IDEs are compatible with record-session?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for record-session?

Requires prerequisites to be confirmed before acting. Must be used after human analysis. Limited to post_commit phase.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add TbK0ng/mytrellis/record-session. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use record-session immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

record-session

Install record-session, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Skill Contract

  • inputs: User request and repository context relevant to this skill.
  • outputs: A concrete action or summary aligned with the skill objective.
  • pre_checks: Confirm prerequisites and read referenced docs/scripts before acting.
  • post_checks: Verify completion, summarize outcomes, and surface follow-up items.
  • writes_artifacts: true
  • uses_memory: true
  • required_phase: post_commit

[!] Prerequisite: This skill should only be used AFTER the human has tested and committed the code.

AI must NOT execute git commit - only read history (git log, git status, git diff).


Record Work Progress (Simplified - Only 2 Steps)

Step 1: Get Context

bash
1uv run ./.trellis/scripts/get_context.py

Step 2: One-Click Add Session

bash
1uv run ./.trellis/scripts/add_session.py \ 2 --title "Session Title" \ 3 --commit "hash1,hash2" \ 4 --summary "Brief summary of what was done"

Step 3: Sync Session Memory (Required)

bash
1uv run ./.trellis/scripts/task.py memory-add-resource current "trellis://workspace/" "Session update anchor" 2uv run ./.trellis/scripts/task.py memory-search current "latest completed work and follow-up actions" --limit 3 3uv run ./.trellis/scripts/task.py memory-commit current --wait-processed-timeout 20

Auto-completes:

  • [OK] Appends session to journal-N.md
  • [OK] Auto-detects line count, creates new file if >2000 lines
  • [OK] Updates index.md (Total Sessions +1, Last Active, line stats, history)

Archive Completed Task (if any)

If a task was completed this session:

bash
1uv run ./.trellis/scripts/task.py archive <task-name>

Script Command Reference

CommandPurpose
uv run ./.trellis/scripts/get_context.pyGet all context info
uv run ./.trellis/scripts/add_session.py --title "..." --commit "..."One-click add session (recommended)
uv run ./.trellis/scripts/task.py memory-commit currentPersist OpenViking memory after session record
uv run ./.trellis/scripts/task.py create "<title>" [--slug <name>]Create new task directory
uv run ./.trellis/scripts/task.py archive <name>Archive completed task
uv run ./.trellis/scripts/task.py listList active tasks

Related Skills

Looking for an alternative to record-session or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer