跳到正文
cccskills
免费在 GitHub 公开

feature-demo

Record product demos that show real user actions and responses for each covered user journey. Add timed captions, inspect the finished clips, and include them in pull requests, with manual test instructions when recording is blocked.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Record at least one captioned demo for every covered CUJ through its real entry point.

查看安装方法

适用场景

  • Showing a feature's real user flow in a pull request
  • Recording CLI or API behavior in a terminal
  • Adding action and result captions to demo clips
  • Documenting manual tests when recording is blocked

包含的文件(1)

  • SKILL.md2.4 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Demo recordings

The demo is required. Record at least one clip for every covered CUJ; a CUJ with several entry points or steps may have more. Each clip shows the user action and the product's response through the CUJ's real entry point, never pytest output, assertions, test source, or debug logs.

Follow dev/recording-lanes.md for the recorder, the per-surface mechanics, and captioning. Use the CUJ ID as the facet and demo as the kind:

  • Save each raw capture as recordings/<ticket-key>/raw/demo-<cuj>.<ext> (add a short suffix, e.g. demo-cuj-1-edit, for extra clips of the same CUJ).
  • Burn timed captions into each clip with dev/caption_recording.py, rendering to recordings/<ticket-key>/demo-<cuj>.mp4. Captions list the actions shown and end with the observed result.
  • Play and inspect each render before declaring it in the handoff and PR Demo. If captioning fails, use the guide's uncaptioned fallback path and say why in that clip's caption and the PR Demo. A usable uncaptioned clip still counts.
  • For API or configuration CUJs, record a VHS terminal session that runs the real CLI or API call and shows its output. Written evidence alone is not a demo.
  • Build the SPA before starting the recorder. Inside a server-spawned runner (OMNIGENT_RUNNER_ID is set), strip the inherited runner variables as the guide describes, and retry before reporting a blocker.

Never commit recordings; upload them to the PR as described in feature-publish.

When a recording can't be made

Recording should almost always work. When a covered CUJ really can't be recorded (the recorder can't start in this environment, or the surface needs hardware or an external account the sandbox doesn't have), still publish a ready PR and drive it as usual. For that CUJ:

  • set recording_blocker to the specific blocker, with the command and error;
  • write manual_test: step-by-step instructions a human can follow to test the journey, including setup, the inputs to give, and what they should see;
  • put both in the PR's Demo section in place of the clip.

The outcome is then partially_implemented, with that CUJ's recording in remaining_work. Only declare clips you actually produced. Then load feature-publish.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.

中文简介正在准备中。当前显示英语简介。

  • Testing message delivery from the web interface to agy
  • Checking terminal output against mirrored session replies
  • Verifying permission requests and interruption
omnigent-ai/omnigent1.1万2026年10月19日 更新

Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.

中文简介正在准备中。当前显示英语简介。

  • Test authentication and real Gemini responses
  • Verify tool connections and sub-agent delegation
  • Investigate model selection failures
omnigent-ai/omnigent1.1万2026年10月19日 更新

api-docs

免费

Create reference documentation directly from source code for public functions, classes, command-line commands, and endpoints. Organize parameters, defaults, return values, errors, and runnable examples, then check that the documentation matches the implementation.

中文简介正在准备中。当前显示英语简介。

  • Writing reference docs for a public module
  • Documenting command-line arguments and defaults
  • Adding minimal usage examples for an API
omnigent-ai/omnigent1.1万2026年10月19日 更新

Create an Omnigent agent directory using validated templates for configuration and instructions. Choose how the agent runs, then add web search, shell access, external tool connections, or subagents only when the task requires them.

中文简介正在准备中。当前显示英语简介。

  • Creating a minimal Omnigent agent
  • Configuring an agent with web search
  • Adding shell access or MCP tool connections
omnigent-ai/omnigent1.1万2026年10月19日 更新

changelog

免费

Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.

中文简介正在准备中。当前显示英语简介。

  • Write release notes covering changes since the last tag
  • Summarize pull requests merged during a selected period
  • Highlight breaking changes before an upgrade
omnigent-ai/omnigent1.1万2026年10月19日 更新

Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.

中文简介正在准备中。当前显示英语简介。

  • Reproducing a first-run setup problem
  • Inspecting menus in a narrow terminal
  • Checking help text and command visibility
omnigent-ai/omnigent1.1万2026年10月19日 更新

查看 omnigent-ai 的全部技能

报告此技能的问题