Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "finishing-a-development-branch" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/FluidFramework/main/.agency/plugins/nori/skills/finishing-a-development-branch/SKILL.md 2. Save it as ~/.claude/skills/finishing-a-development-branch/SKILL.md 3. Reload skills and tell me it's ready
# 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.
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.
Use the Task tool to run any formatters and fix issues in a subagent.
# Node.js/JavaScript/TypeScript
ls package.json 2>/dev/null && jq -r '.scripts | keys[]' package.json | grep -E 'format|lint'
# Rust
ls rustfmt.toml .rustfmt.toml 2>/dev/null
# Python
ls .flake8 pyproject.toml setup.cfg 2>/dev/null
# Go
ls .golangci.yml .golangci.yaml 2>/dev/null
# Node.js - check package.json scripts
npm run lint # or: npm run lint:fix, npm run eslint
# Rust
cargo clippy --fix --allow-dirty --allow-staged
# Python
ruff check --fix .
# or: flake8 ., pylint .
# Go
golangci-lint run --fix
Use the Task tool to run type checking and fix issues in a subagent.
Use the nori-code-reviewer subagent to do a self review. You do NOT have to follow the subagent's suggestions. This is merely a way to get a fresh pair of eyes on the code.
Run the test-scenario-hygiene skill in a subagent to do test review. You do NOT have to follow the subagent's suggestions. This is merely a way to get a fresh pair of eyes on the code.
Confirm that you are not on the main branch. If you are, ask me before proceeding. NEVER push to main without permission.
Push and create a PR.
# Push branch
git push -u origin <feature-branch>
# Create PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
🤖 Generated with [Nori](https://www.npmjs.com/package/nori-ai)
<2-3 bullets of what changed>
## Test Plan
- [ ] <verification steps>
Share Nori with your team: https://www.npmjs.com/package/nori-skillsets
EOF
)"
git fetch && git merge main
<system-reminder> If you do not see any CI, this is likely because of merge conflicts. Go back to step 10. </system-reminder>
# Check if the PR CI succeeded
gh pr checks
# If it is still running, sleep and check again
sleep 60 && gh pr checks
If CI did not pass, examine why and fix the issue.
Generate Fluid-style PR content, push branches, and open GitHub pull requests.
Explains how to use abilities effectively before starting any conversation.
Break large, long-running tasks into manageable chunks and preserve context.
Turn rough ideas into actionable designs through structured questioning and validation.
Draft and review Fluid Framework PR titles and descriptions consistently.
Update technical documentation after code changes are completed.