تشغيل أي مهارة في Manus بنقرة واحدة

arn-shipping

النجوم٢٨

التفرعات٣

آخر تحديث١٨ مايو ٢٠٢٦ في ١٢:١٠

This skill should be used when the user says "shipping", "arness shipping", "ship it", "ship", "create PR", "open pull request", "push and PR", "commit and push", "wrap up", "ship the feature", "ship the fix", "ready to ship", "push changes", "finalize", "finish up", "done", "arn-shipping", or wants to commit, push, and optionally create a pull request. Handles branching, staging, committing, pushing, and PR creation as a single guided flow. Chains from arn-implementing at completion.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

AppsVortex

AppsVortex/arness

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	arn-shipping
description	This skill should be used when the user says "shipping", "arness shipping", "ship it", "ship", "create PR", "open pull request", "push and PR", "commit and push", "wrap up", "ship the feature", "ship the fix", "ready to ship", "push changes", "finalize", "finish up", "done", "arn-shipping", or wants to commit, push, and optionally create a pull request. Handles branching, staging, committing, pushing, and PR creation as a single guided flow. Chains from arn-implementing at completion.
version	1.0.0

Arness Shipping

Commit, push, and optionally create a pull request. This is a first-citizen entry point that wraps arn-code-ship and provides chaining context to the next stage (arn-reviewing-pr).

This skill is a thin orchestration wrapper. It MUST NOT duplicate arn-code-ship logic. All shipping work is done by the invoked skill. Arness-shipping handles: prerequisite checks, invoking the ship skill, and informing the user about the next stage.

Step 0: Ensure Configuration

Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-code-ensure-config/references/step-0-fast-path.md and follow its instructions. This guarantees a user profile exists and ## Arness is configured with Arness Code fields before proceeding.

Workflow

Step 1: Invoke Ship

Show progress:

Shipping: SHIP (branch -> stage -> commit -> push -> PR)
          ^^^^

Invoke the ship skill:

Skill: arn-code:arn-code-ship

The ship skill handles all internal decisions: branching, staging, commit message generation, pushing, and PR creation. It has its own user interactions. Wait for it to complete.

Step 2: Completion Handoff

After arn-code-ship completes, present the chain exit:

"When your PR gets review feedback, run /arn-reviewing-pr to validate and address comments."

Error Handling

## Arness config missing: Handled by Step 0 (ensure-config) — this should not occur if Step 0 completed successfully.
arn-code-ship fails: Present the error. Ask: retry or abort.
Nothing to ship (clean tree, no commits ahead): arn-code-ship handles this internally — it will inform the user. No action needed at this level.

المزيد من هذا المستودع

نفس المستودع

arn-code-batch-cve-fix

AppsVortex/arness

This skill should be used when the user says "fix CVEs", "patch vulnerabilities", "apply security patches", "resolve security advisories", "batch CVE fix", "patch dependencies", "fix security findings", "remediate CVEs", "apply CVE fixes", "batch fix vulnerabilities", "resolve vulnerability tickets", "arness CVE fix", "arn-code-batch-cve-fix", "fix all open CVE tickets", "cleanup resolved CVE proposals", or wants Arness to apply per-group dependency bumps for previously-triaged CVEs and open per-group pull requests that close their corresponding sub-issues. Reuses arn-code-batch-implement worker isolation verbatim, opens PRs targeting the configured Security branch, and offers an interactive post-merge cleanup of fully-resolved past CVE proposals. Interactive only — no proposal mode, no headless write path; every PR is human-reviewed and every archive move is confirmed via AskUserQuestion. Requires that arn-code-batch-cve-scan has produced triage records and sub-issues.

2026-07-0528

arn-code-batch-cve-scan

AppsVortex/arness

This skill should be used when the user says "scan for CVEs", "CVE scan", "check for vulnerabilities", "find vulnerabilities", "check security advisories", "dependabot triage", "dependabot scan", "scan dependencies for security issues", "audit dependencies", "vulnerability triage", "security scan", "run security audit", "arness CVE scan", "arn-code-batch-cve-scan", "run a scheduled CVE scan", "produce a CVE proposal", "finalize a CVE proposal", or wants Arness to discover, triage, and ticket security advisories across project dependencies. Supports three modes (interactive, proposal, finalize) so the workflow is safe to schedule unattended via Claude Code Routines and tool-agnostic enough to drive headlessly via claude -p or any LLM-running CLI. Dual-source discovery (GitHub Dependabot plus locally-detected scanners), per-CVE triage via arn-code-cve-analyst, project-native waiver capture, and pre-triage parent plus per-group sub-issue ticketing on GitHub or Jira. Reads from the configured Security branch.

2026-07-0528

arn-code-ensure-config

AppsVortex/arness

This skill should be used when the user says "ensure config", "check arness config", "arn-code-ensure-config", "verify arness setup", or wants to verify that Arness Code configuration is present for the current project. This skill is primarily consumed as a reference by entry-point skills (arn-planning, arn-implementing, arn-shipping, arn-reviewing-pr, arn-assessing, arn-code-feature-spec, arn-code-bug-spec, arn-code-swift, arn-code-standard) which read the `references/step-0-fast-path.md` reference as Step 0 before proceeding with their workflow.

2026-07-0528

arn-code-init

AppsVortex/arness

Optional customization and upgrade tool. This skill should be used when the user says "initialize arness code", "arness code init", "arn-code-init", "init arness code", "setup arness code", "arness code setup", "set up arness code", "start arness code", "upgrade arness code", "update arness code", "configure arness code for this project", "add arness code to this project", "reconfigure arness code", "review arness config", "customize arness config", "arness settings", or wants to customize Arness configuration, review current settings, or upgrade after a plugin update. Handles both existing codebases (analyzes patterns) and greenfield projects (recommends patterns based on technology choices). Also handles upgrades after plugin updates.

2026-07-0528

arn-infra-ensure-config

AppsVortex/arness

This skill should be used when the user says "ensure config", "check arn infra config", "arn-infra-ensure-config", "verify arn infra setup", or wants to verify that Arness Infra configuration is present for the current project. This skill is primarily consumed as a reference by entry-point skills (arn-infra-wizard, arn-infra-assess) which read the `references/step-0-fast-path.md` reference as Step 0 before proceeding with their workflow.

2026-07-0528

arn-spark-ensure-config

AppsVortex/arness

This skill should be used when the user says "ensure config", "check arn spark config", "arn-spark-ensure-config", "verify arn spark setup", "configure spark", "setup arness spark", "spark config", or wants to verify that Arness Spark configuration is present for the current project. This skill is primarily consumed as a reference by entry-point skills (arn-brainstorming, arn-spark-discover, arn-spark-arch-vision) which read the `references/step-0-fast-path.md` reference as Step 0 before proceeding with their workflow.

2026-07-0528

name	arn-shipping
description	This skill should be used when the user says "shipping", "arness shipping", "ship it", "ship", "create PR", "open pull request", "push and PR", "commit and push", "wrap up", "ship the feature", "ship the fix", "ready to ship", "push changes", "finalize", "finish up", "done", "arn-shipping", or wants to commit, push, and optionally create a pull request. Handles branching, staging, committing, pushing, and PR creation as a single guided flow. Chains from arn-implementing at completion.
version	1.0.0

Arness Shipping

Commit, push, and optionally create a pull request. This is a first-citizen entry point that wraps arn-code-ship and provides chaining context to the next stage (arn-reviewing-pr).

Step 0: Ensure Configuration

Workflow

Step 1: Invoke Ship

Show progress:

Shipping: SHIP (branch -> stage -> commit -> push -> PR)
          ^^^^

Invoke the ship skill:

Skill: arn-code:arn-code-ship

The ship skill handles all internal decisions: branching, staging, commit message generation, pushing, and PR creation. It has its own user interactions. Wait for it to complete.

Step 2: Completion Handoff

After arn-code-ship completes, present the chain exit:

"When your PR gets review feedback, run /arn-reviewing-pr to validate and address comments."

Error Handling

## Arness config missing: Handled by Step 0 (ensure-config) — this should not occur if Step 0 completed successfully.
arn-code-ship fails: Present the error. Ask: retry or abort.
Nothing to ship (clean tree, no commits ahead): arn-code-ship handles this internally — it will inform the user. No action needed at this level.