branch-lifecycle
Skill2 starsChanged 4 days agoMITView on GitHub
When a session creates, integrates or closes a task branch or worktree, verify the project branch contract, candidate identity, integration evidence and safe removal conditions. Session takeover and handover use context-handoff; material retention and recovery use archive-maintenance. Ordinary implementation commits use task-implementation and release acceptance uses release-readiness.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- haintbotast/coding-agent-instructionstheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- haintbotast/coding-agent-instructions★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- ai-trace-auditSkill
- ai-workspace-governanceSkill
- archive-maintenanceSkill
- change-reviewSkill
- cloud-api-integrationSkill
- code-security-reviewSkill
- coding-conventionsSkill
- container-image-managementSkill
- context-budgetSkill
- context-handoffSkill
- deployment-patternsSkill
- docker-local-environmentSkill
- documentation-authoringSkill
- estimationSkill
- external-dependency-simulationSkill
- gitlab-webhook-local-gitSkill
- go-patternsSkill
- go-testingSkill
- grpc-proto-contractSkill
- guided-evidence-collectionSkill
- http-api-designSkill
- jenkins-pipeline-jjbSkill
- ldap-rbacSkill
- mysql-migration-safetySkill
- plan-designSkill
- plan-outlineSkill
- plan-reviewSkill
- playwright-e2eSkill
- project-contextSkill
- pytest-patternsSkill
- redis-patternsSkill
- release-readinessSkill
- role-bootstrapSkill
- skill-maintenanceSkill
- subtask-dispatchSkill
- systematic-diagnosisSkill
- task-implementationSkill
- test-strategySkill
- verification-gateSkill
- vue3-developmentSkill
- vue-testingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. About 0 are common, 20 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈20
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 10
Keep task history reachable and integration traceable under the project's authorised branch model.
- Distinctive: line 28
Use context-handoff for session recovery, write transfer and continuation records.
- Distinctive: line 30
Use task-implementation for implementation, checks and local resource cleanup.
- Distinctive: line 31
Use release-readiness for acceptance and the release decision.
- Distinctive: line 32
Use archive-maintenance for task materials, register retention and historical recovery.
- Distinctive: line 37
Use only the input contract's branch names and integration topology.
- Very specific: line 39
Never assume that main means deployed code or that dev must exist.
- Distinctive: line 41
Do not commit on detached HEAD.
- Distinctive: line 43
Do not rebase pushed branches, rewrite published history, move immutable release/archive tags or force push.
- Distinctive: line 44
Before any fetch, pull or push, verify the actual destination against the supplied central address.
- Distinctive: line 45
Use fast-forward-only pulls.
- Distinctive: line 51
Verify the allowed worktree location and actual baseline commit/tree before creating the task branch.
- Distinctive: line 52
Use the project's naming convention and register only this task's worktree, branch and writer association.
- Distinctive: line 60
Read the project's requirements for security and compatibility review.
- Distinctive: line 66
Use an authorised abort only when returning an in-progress operation to its prior clean state is required.
- Distinctive: line 67
Run required integration checks and record any authorised push's actual outcome.
- Distinctive: line 71
Verify all associated executions have ended, all required checks passed and the intended result remains reachable at the required …
- Very specific: line 72
After cherry-picking, verify the source-to-result mapping.
- Distinctive: line 74
Remove only this task's registered clean worktrees with ordinary git worktree remove.
- Distinctive: line 75
Delete only the verified integrated branch under the project's Git policy.
- Distinctive: line 97
Never move an existing release tag to represent another release.
- Very specific: line 102
Keep incomplete steps in their actual state.
- Very specific: line 107
Do not stash, discard, force-remove or label those files archived automatically.
- Distinctive: line 116
No directly adopted external source.
- Very specific: line 119
No third-party license file is required.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Branch and worktree lifecycle
Keep task history reachable and integration traceable under the project's authorised branch model. This method grants no Git, deletion, dispatch or release permission. It does not choose a new branch model for an existing repository.
Inputs and boundaries
Take these values from the consuming project's contract:
- Repository, primary working copy, central repository address and permitted Git operations.
- Task ID, baseline commit/tree, branch names and the authorised file scope.
- Worktree layout, existing register and the permitted writers for task, integration and release refs.
- Current branch/worktree inventory, uncommitted and untracked files, execution state and pinned review evidence.
- Any closure deadline, inactivity threshold, register retention policy and reporting destination.
Missing repository, path or authority -> locate the contract before the dependent write. Missing timing or retention parameters -> keep them unknown; do not invent expiry periods. A branch-model mismatch -> report it before changing refs; this package does not authorise migration. Unknown or active conflicting execution -> preserve the worktree and branch. Use context-handoff for session recovery, write transfer and continuation records.
Use task-implementation for implementation, checks and local resource cleanup. Use release-readiness for acceptance and the release decision. Use archive-maintenance for task materials, register retention and historical recovery. An archive tag preserves a commit graph; it cannot preserve uncommitted or untracked files.
Ref safety
Use only the input contract's branch names and integration topology.
A repository with a separate integration branch and a repository integrating directly to its primary branch need different targets.
Never assume that main means deployed code or that dev must exist.
- Do not commit on detached HEAD; a read-only reviewer may inspect a pinned detached commit.
- Integrate with an authorised ordinary merge or
cherry-pick -x, retaining the source relationship. - Do not rebase pushed branches, rewrite published history, move immutable release/archive tags or force push.
- Before any fetch, pull or push, verify the actual destination against the supplied central address.
- Use fast-forward-only pulls; divergence or non-fast-forward rejection leaves the step pending.
- Push only explicitly authorised refs; branch creation or successful local integration does not imply push permission.
Execute the lifecycle
- Create and register.
Verify the allowed worktree location and actual baseline commit/tree before creating the task branch.
Use the project's naming convention and register only this task's worktree, branch and writer association.
A name collision or different existing baseline -> preserve it and resolve ownership first.
On re-entry, recover the existing object through
context-handoff; do not create a duplicate task branch. - Freeze a candidate. The task writer accounts for intended tracked, untracked and deleted files before recording HEAD/tree. A commit identity does not cover residual working-tree changes. Independent checks bind to that candidate; changed bytes require a new candidate and affected checks. Read the project's requirements for security and compatibility review; this method does not self-sign them.
- Integrate verified results. The authorised integrator verifies source identity, review scope and the current target state. Record source and resulting commits for both merge and cherry-pick integration. On conflicts, stop integration and report the affected files; do not silently choose a side or change unrelated files. Use an authorised abort only when returning an in-progress operation to its prior clean state is required. Run required integration checks and record any authorised push's actual outcome. Rejection or unknown outcome remains pending and blocks claims that the central result is delivered.
- Close registered objects safely.
Verify all associated executions have ended, all required checks passed and the intended result remains reachable at the required destination.
After cherry-picking, verify the source-to-result mapping; ancestry alone is insufficient.
Preserve task materials and residual files under
archive-maintenancebefore any destructive removal. Remove only this task's registered clean worktrees with ordinarygit worktree remove. Delete only the verified integrated branch under the project's Git policy. A failed safe deletion check -> keep the object and report the blocker; do not force removal. Record actual closure time only after closure succeeds. - Preserve abandoned history.
Confirm the abandonment decision and preservation requirements through
archive-maintenance. Where the contract uses archive refs, create the immutable ref at the exact retained tip and verify required central reachability before branch deletion. A same-name tag pointing elsewhere -> stop; never move it. Apply the same stopped-writer and clean-worktree conditions as normal closure. Dirty or untracked material needs separate preservation; a tag is insufficient. - Assess inactivity. Compare age only with the supplied threshold and record actual execution state. Age alone never authorises deletion or proves the task is abandoned. Report the task identity, worktree, history identity and uncertainty for the authorised decision maker. Missing threshold -> give the inventory without classifying it as expired.
Release refs and completion evidence
Release acceptance remains in release-readiness; this package only updates the refs authorised by the project's release contract.
Pin the accepted and, where relevant, actually deployed identity before moving a release ref.
Unknown identity, missing acceptance or a required fast-forward that fails -> stop those ref changes.
Never move an existing release tag to represent another release.
Reuse the existing task register rather than creating a second state store.
Record task/worktree/branch, baseline, writer association, frozen candidate, source-to-integration mapping,
review locators, actual ref/push outcomes, removed and retained objects, closure time and blockers.
Keep incomplete steps in their actual state; report blocked closure before any project deadline.
Material retention and removal of expired closed register rows follow archive-maintenance and the supplied retention contract.
A dirty worktree discovered after integration stays in place.
Record the already integrated result and residual changes separately, then resolve preservation within authorised scope.
Do not stash, discard, force-remove or label those files archived automatically.
Other local resources use the cleanup rules of task-implementation; never run global cleanup.
Routine inventory suits low/low; integration conflicts and uncertain history mapping suit normal/high.
Grade words map to actual execution configuration through the project resource mapping.
Executor availability and environment limits come from the project; this method does not launch sessions.
Sources
- No directly adopted external source; this package is own-authored.
- The parameterised ref/worktree lifecycle, integration mapping and safety decisions are own-authored, pending host behaviour verification. Branch names, topology, deadlines and register states are project inputs; handover and material retention remain in their named packages.
- No third-party license file is required; the root LICENSE applies. The library's third-party summary is THIRD_PARTY_NOTICES.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

