跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

project-continuity

Maintain AI-KIT's own context, template boundaries, and installer verification when kit structure or procedures change.

tigusigalpa · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add tigusigalpa/ai-kit --skill project-continuity

技能说明


name: project-continuity description: Maintain AI-KIT's own context, template boundaries, and installer verification when kit structure or procedures change.

AI-KIT maintenance continuity

Read contribution rules. Read optional local ../../../PROJECT_CONTEXT.md, ../../../AGENTS.md and ../../../WIKI.md when present; otherwise verify facts from public source/configuration. These three root files stay local and untracked, outside wheel/Docker payloads; their template counterparts stay public. Check distributions with and without local copies and preserve their on-disk bytes when untracking. Keep the root context/history about this kit; keep template project facts uninitialized. Sync commands, this skill, docs, context and WIKI on procedure/fact/agreement changes; keep facts in context. Keep release receipts (commits, workflow runs, hashes, digests) in docs/V*.md and link them; context holds current facts, commands and agreements only. Validate templates/links/registry, the agent registry (integrations/agents.json), and behavioral installation scenarios; record root CHANGELOG entries. Keep the root SKILL.md (the repository as a skill) consistent with the CLI, presets, extras, and policies. Review explicit semantic acceptance and future-upgrade conflicts whenever installer baseline behavior changes. Check candidate draft preservation, state/settings validation, and adapter retirement conflicts when changing installation. Exercise installed Git visibility and portable linked-path refusal; distinguish synthetic fixtures from real application trials. Verify the conditional Docker trigger in installed AGENTS and preserve edited entry points during upgrades. Exercise file-versus-directory native rule layouts on both probe and selected-write paths: simulate POSIX ENOTDIR on Windows, preserve existing file markers and rerun stability, and refuse blocked selected parents before writes. Do not hide permission failures or linked-path refusals during optional adapter probes; see file-parent compatibility. Exercise manifest-based profile detection and project-fact drafts (version/commands into PROJECT_CONTEXT and project.json), scoped Node/Python ignore rules, the installed-project doctor report, opt-in extras (session-start, guards, CI) including key-level client settings merges, legacy whole-file migration, and hook execution, client detection markers, interactive/check onboarding, the adr/changelog helpers, and the offline router helper (route/configure with provider selection) when installer behavior changes. For generated client configuration, exercise private/team settings files and mode switches, owned-entry moves, project.json precedence, secret lists, ignore blocks, every scoped rule format with root modules and skipped paths, presets that turn extras off, and workflow skill copies; recheck client formats against primary docs before changing them. For routing, compare the implementation ladder with canonical POLICY, exercise English/Russian operation/risk regressions and override precedence, provider-review status/sources, and distinguish recommendations from executed model controls. For stack profiles, exercise manifest evidence, module scoping, and command drafting; for Filament specifically test Composer dependency/lock evidence and source/native skill lifecycle. For optional metrics, verify failure/recovery accounting, missing-value coverage, duplicate/lock/path guards, private/team journal visibility, schema 1/2 compatibility, experiment/arm/task identity, per-provider analyze output, and upgrade preservation. Exercise context snapshots and doctor warnings for new/removed modules, profile drift, and manifest changes. Exercise adapter reports plus explicit retirement of unchanged files, backups/state updates, and modified-file conflicts. Exercise opaque evaluator pair coverage without task-text persistence. Use the evaluation protocol for separately authorized application trials; synthetic fixtures establish no savings. For language/identifier/client changes, verify fresh English and preserved saved languages, JavaScript/Node.js versus browser evidence, cross-stack --with-uuid opt-in, and --with-claude-github persistence without login/Git mutation. Claude commit attribution is an owned singleton scalar; preserve custom-value conflicts, human identity/signing and unrelated PR settings across private/team moves. Test Devin (Windsurf) .devin rules, legacy .windsurf coexistence and explicit retirement without deleting adapted files. Keep TypeUI setup in the README source-checked against vendor MCP/auth/scope docs; installation does not establish live activation. Record runtime gaps separately from static/source checks. For measurement-led changes, test schema 1/2/3 compatibility, fixed A/B controls, immutable Git blobs and isolated repeated workspaces, missing/estimated telemetry, semantic-review gates, interrupted runs and idempotent private exports. Exercise resume identity checks, per-unit failure recording and configurable kit-arm agents/presets. Check that worker Git discovery cannot reach the source through parents: a ceiling at cwd itself is ineffective. Keep worker requests separate from observed execution. Exercise routing modes/pins/profiles, distinct-case quality floors, matched history, unsupported controls, immutable proposal history and explicit backed-up restore. Exercise module context scope, duplicate content, critical rules/ADRs above byte budgets and linked paths. Follow the staged plan and worker contract; keep native activation and real trials separate. For optional orchestration, test opt-in/persistence, Codex helper conflicts/retirement, private/team/archive exclusions, bounded inputs/keys/budgets, reservations/locks, unknown billing, source-bound review and reco

阅读完整来源 ↗