Skip to main content

project-maintenance

Guides in-place enhancement, extraction, and version upgrades for projects generated by Agent Starter Pack.

الانتقال إلى التثبيت

معلومات المصدر

المستودع
VectorSpaceLab/AREX-Skill
آخر نشاط في المصدر
٢٦ أغسطس ٢٠٢٦ في ١٦:٣١
لغة SKILL.md المكتشفة
الإنجليزية
النجوم
١٢
التفرعات
٢

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

مستكشف الملفات
3 ملفات

عرض SKILL.md

SKILL.md
تعليمات المصدر · معاينة للقراءة فقط
name
project-maintenance
description
Guides in-place enhancement, extraction, and version upgrades for projects generated by Agent Starter Pack.
metadata
{"disco-role":"operating"}
disable-model-invocation
true
license
Apache 2.0
# Project maintenance Use this sub-skill when the user already has an Agent Starter Pack project and wants to modify, shrink, or upgrade it. ## Covers - `enhance` for templating Agent Starter Pack capabilities into an existing project. - `extract` for turning a scaffolded project into a minimal shareable agent. - `upgrade` for merging a generated project forward to a newer ASP version. - Backup, version-lock, language-detection, metadata, and 3-way merge behavior that make those workflows safe. ## Excludes - Choosing a template for a brand-new project belongs in `project-scaffolding`. - CI/CD provisioning, deployment, and Gemini Enterprise registration belong in `deployment-ops`. ## Read first - `../../references/cli-reference.md` for command ownership. - `../../references/package-overview.md` for install and sanity-check guidance. - `references/workflows.md` for the enhancement, extraction, and upgrade flows. - `references/troubleshooting.md` for backup, merge, metadata, and version-lock failures. ## Common workflow 1. Determine whether the user is enhancing, extracting, or upgrading. 2. Check the project metadata and current layout before changing anything. 3. Use backups or dry-run modes when available. 4. Prefer the merge logic already built into the package rather than inventing a custom file strategy. 5. Hand off cloud-deployment questions to `deployment-ops` after the local project state is correct. ## Useful signals - `enhance`, `--base-template`, `--agent-directory`, `--dry-run`, `--prefer-new`, `--force` - `extract`, `--source`, `--force`, `--dry-run` - `upgrade`, `asp_version`, `--dry-run`, `--auto-approve` - backup, conflict, merge, metadata, or version-lock language ## Validation mindset - Do not assume every generated project uses the same language or directory layout. - Treat missing metadata or version markers as a workflow problem that needs the maintenance reference, not as a template-selection issue. - If the user only needs to understand the generated project’s deployment commands, route to `deployment-ops`.
عرض على GitHub