skill finish branch

Engineering Community

Skill notes

Execution Contract (MANDATORY - CANNOT SKIP)

This generated Codex skill preserves an enforced workflow contract from the source skill. PROHIBITED: Do not summarize, simulate, or skip the referenced workflow command when this skill requires execution. Do not claim provider output or validation artifacts exist without checking the actual files or command output. Do not continue silently when a required provider, command, or host capability is unavailable; report the unavailable dependency and use a supported fallback.

Overview

Full ship pipeline: tests → multi-provider review → version bump → changelog → commit → push → PR. Core principle: Verify tests → Review diff → Bump version → Update changelog → Present options → Execute choice → Clean up.

Step 1: Verify Tests Pass

Before anything else, verify tests pass: If tests fail: STOP. Show failures. Do not proceed. If tests pass: Continue to Step 2.

Step 2: Multi-Provider Diff Review

Run a quick multi-provider review of the changes before shipping. This catches issues before they reach PR reviewers. Always run a quick review — this is automatic, not optional: If critical issues found: Present them and ask whether to fix or ship anyway. If clean: Continue to Step 3. Show a brief ✓ Review clean — no issues found.

Step 4: Version Bump & Changelog (Optional)

If a VERSION file or package.json exists, offer to bump: If bumping: Update the version file and prepend a changelog entry summarizing the diff:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nyldn · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Verify Tests Pass

Before anything else, verify tests pass: If tests fail: STOP. Show failures. Do not proceed. If tests pass: Continue to Step 2.

02
Step 2: Multi-Provider Diff Review

Run a quick multi-provider review of the changes before shipping. This catches issues before they reach PR reviewers. Always run a quick review — this is automatic, not optional: If critical issues found: Present them and ask whether to fix or ship anyway. If clean: Continue to Step 3. Show a brief `✓ Review clean — no issues found`.

03
Step 3: Determine Base Branch & Version

Step 3: Determine Base Branch & Version

04
Step 4: Version Bump & Changelog (Optional)

If a VERSION file or package.json exists, offer to bump: If bumping: Update the version file and prepend a changelog entry summarizing the diff:

05
Step 5: Present Options

Present exactly these 4 options: Keep options concise. Don't add explanations unless asked.

06
Step 4: Execute Choice

Option 1: Merge Locally Report: Option 2: Create PR Report: Option 3: Keep As-Is

07
Step 5: Cleanup (If Using Worktrees)

For Options 1, 2, 4: Check if in a worktree and clean up: For Option 3: Keep worktree intact.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.