sdlc-commit

Seals integration changes and fast-forwards the feature branch to the verified tip without pushing.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-commit-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-commit
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/sdlc-commit
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-commit-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Completing an Agentic SDLC feature requires a safe local commit checkpoint: sealing any final integration changes, promoting the unchanged project branch to the exact verified tip, and cleaning up integration worktrees without risking force operations, pushes, or history rewrites. ## Core Features & Use Cases - Sealed Integration Commit: Creates at most one final integration commit with a message referencing FEAT-* and REQ-* IDs, guarded by a short-lived commit-authorization file. - Fast-Forward-Only Promotion: Promotes the project feature branch to the exact recorded SHA under a shared Git common-directory lock, with precheck and postcheck verification. - Non-Force Cleanup: Removes the integration worktree and deletes its branch only at the exact expected promoted SHA, never using force. - Use Case: After all SDLC waves pass validation, tests, and evaluation, the coordinator invokes this skill to seal the integration tip, fast-forward the feature branch, record commit evidence, and transition the feature state to committed. ## Quick Start Ask the Agentic SDLC coordinator to run $sdlc-commit after all validation, test, and evaluation evidence passes for the current feature.

Frequently Asked Questions about sdlc-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit a completed feature in the Agentic SDLC workflow?

Invoke sdlc-commit through the verified SDLC coordinator after validation, tests, and evaluation pass. It seals at most one final integration commit, fast-forwards the feature branch to the exact tip, and records commit evidence with the feature and requirement IDs.

How does fast-forward-only branch promotion work in Git?

The skill runs a precheck, git merge --ff-only to the sealed tip, and a postcheck under a shared Git common-directory lock. Non-fast-forward ancestry maps to PROMOTION_FAILED, so history is never rewritten or force-updated.

Can sdlc-commit push changes or create pull requests?

No. The skill never pushes, creates PRs, or merges externally. It performs only a local commit checkpoint and branch promotion; pushing requires a separate explicit action outside this SDLC local-commit path.

When should I not use sdlc-commit?

Do not use it for ordinary local commits outside Agentic SDLC, before evidence passes, or to squash, rebase, amend, cherry-pick, or force-delete. It also refuses to commit secrets, local run state, or work from a default branch.

Why does sdlc-commit report PROMOTION_BLOCKED or POLICY_BLOCK?

PROMOTION_BLOCKED occurs when the project or integration state moved or is dirty. POLICY_BLOCK results from a default-branch commit attempt, hook denial, or a missing or expired commit-authorization.json guard file.