🔀
DevOpsTypeScript

Finishing a Development Branch

by microsoft

Finishing a Development Branch is a DevOps skill for Claude Code, published by microsoft in FluidFramework.

4.9K stars583 forkson microsoft/FluidFrameworkAdded 2026/07/19Repository updated 2026/08/06
collaborationcrdtdatastructuredistributedfluidfluid-frameworkmicrosoftrealtime
Install in seconds
Install Finishing a Development Branch
Copy Finishing a Development Branch into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/microsoft/FluidFramework/tree/main/.agency/plugins/nori/skills/finishing-a-development-branch ~/.claude/skills/finishing-a-development-branch

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/microsoft/FluidFramework.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
.agency/plugins/nori/skills/finishing-a-development-branch/SKILL.md in microsoft/FluidFramework
Installs to
~/.claude/skills/finishing-a-development-branch
Collection
One of 31 skills cataloged from this repository
Category
DevOps1075 skills

What Finishing a Development Branch does

Automates the workflow for finalizing a development branch: runs tests, formatting, linting, type checking, creates a PR, and ensures CI passes. Ideal for developers ready to submit their feature implementation for review.

Finishing a Development Branch is cataloged under DevOps on DirSkills. Finishing a Development Branch comes from a repository tagged collaboration, crdt, datastructure, distributed and fluid.

Documentation

README

  1. Use the Task tool to verify tests by using the project's test suite.
# Run project's test suite
npm test / cargo test / pytest / go test ./...

If tests fail:

Tests failing (<N> failures). Must fix before creating PR:

[Show failures]

Cannot proceed until tests pass.
  1. Confirm that there is some formatting/lint/typechecking in the project. If NONE of these exist, ask me if there was something that you missed.

  2. Use the Task tool to run any formatters and fix issues in a subagent.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Finishing a Development Branch

  • What else does microsoft publish alongside Finishing a Development Branch?

    Finishing a Development Branch is one of 31 skills that DirSkills catalogs from microsoft/FluidFramework, the repository it ships in. Its siblings there include API Changes Review, Brainstorming and Building UI/UX. Each one is a separate skill with its own page in this directory, installs the same way Finishing a Development Branch does, and is maintained by microsoft in that same repository. The rest of the collection is listed on the microsoft/FluidFramework page.

  • How does Finishing a Development Branch compare to other DevOps skills?

    Finishing a Development Branch ranks #159 by stars among the 1075 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Finishing a Development Branch against them. Open each page to compare what they document and how they install.

More from microsoft/FluidFramework

Finishing a Development Branch is one of 31 skills cataloged on DirSkills from microsoft/FluidFramework.

See all 31 skills