UNPKG

@crossplatformai/skills

Version:

Reusable Agent Skills for CrossPlatform.ai projects.

github.com/crossplatformai/framework

crossplatformai/framework

53 lines (39 loc) • 2.97 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
# Direct-User Ship Use this reference when the user directly instructs Ship to commit staged or unstaged changes without a Build handoff. ## Authority And Scope The current request authorizes Ship to inspect status and diffs, selectively stage clearly related owned hunks, run proportionate non-mutating checks, and create coherent narrative commits. It needs no Post packet, peer review, reviewer metadata, or approval receipt. Authority excludes publication, release or deployment, registry mutation, migration generation or application, temporary-link finalization or unlinking, replacement installation, and unrelated user-owned work. ## Inspection And Staging Inspect fresh `git status --short`, staged and unstaged diffs, untracked content, recent commit conventions, package scope, and ownership. Stage only clearly related existing files or hunks, using patch staging for mixed files. Stop for ambiguous ownership, possible secrets, generated migrations, missing manifest/lockfile pairing, unexplained lockfile churn, or prohibited release-like state. Preserve already coherent commits. When remaining changes contain separable concerns, use multiple narrative commits when their intended story is clear; ask only when partitioning would change the user's intent or ownership is ambiguous. ## Checks Determine reasonable checks from repository instructions, launchers, affected package scripts, and the actual diff. Apply the reuse and invalidation rules in `quality-assurance.md`. A commit operation alone never invalidates a check. A selected-check failure, required unavailable command, or unclassified content mutation blocks the affected commit. ## Commit Message And Verification Use a supplied summary and description when valid. Otherwise draft a Conventional Commit subject and one unwrapped explanatory body paragraph before any footer lines. The body is required for normal authored commits, including when the subject seems self-explanatory. Version-bump commits still require a body but may use multiple paragraphs. A valid temporary-link lifecycle commit may omit its body only with the exact `--TEMP-- type(scope): subject` header. Generated merge, revert, `fixup!`, `squash!`, and `amend!` commits are exempt. Never add `Co-Authored-By` or agent/session attribution trailers, and never use `--no-verify` to bypass the policy. Validate before staging, before committing, and after hooks complete. Self-validate the message; do not launch a separate review process. Immediately before commit, confirm the staged diff contains only its intended owned hunks and capture the pre-commit tree. After commit, compare the commit tree and fresh status to detect hook mutation. Classify and verify any changed content before continuing. Report authority, hashes and subjects, files, checks and results, final tree continuity, remaining dirty-tree classifications, and confirmation that no prohibited release-like or migration action occurred.