Finishing a Development Branch

Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.

8 stars

Best use case

Finishing a Development Branch is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.

Teams using Finishing a Development Branch should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/exampleskill/SKILL.md --create-dirs "https://raw.githubusercontent.com/tilework-tech/nori-lint/main/exampleskill/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/exampleskill/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How Finishing a Development Branch Compares

Feature / AgentFinishing a Development BranchStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

<required>
CRITICAL Add the following steps to your Todo list using TodoWrite:

1. Use the Task tool to verify tests by using the project's test suite.

```bash
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.
```

2. 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.

3. Use the Task tool to run any formatters and fix issues in a subagent. Check for formatter config files based on the project language.

4. Use the Task tool to run any linters and fix issues in a subagent. Run the appropriate linter for the project language.

5. Use the Task tool to run type checking and fix issues in a subagent.

6. 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.

7. Confirm that you are not on the main branch. If you are, ask me before proceeding. NEVER push to main without permission.

8. Push and create a PR.

```bash
git push -u origin [feature-branch]

gh pr create --title "[title]" --body "$(cat <<'EOF'
## Summary
🤖 Generated with Nori

<2-3 bullets of what changed>

## Test Plan
- [ ] <verification steps>
EOF
)"
```

9. Merge main and resolve conflicts if necessary.

```bash
git fetch && git merge main
```

10. Make sure the PR branch CI succeeds.

```bash
gh pr checks

sleep 60 && gh pr checks
```

If CI did not pass, examine why and fix the issue.

- Make changes as needed, push a new commit, and repeat the process.
<system-reminder> It is critical that you fix any ci issues, EVEN IF YOU DID NOT CAUSE THEM. </system-reminder>

11. If this was a change to a webapp, spin up the server and the ui in a demo localhost link and show me the link so that I can review the changes.

12. Tell me: "I can automatically get review comments, just let me know when to do so."
</required>

Related Skills

python-development

16
from plurigrid/asi

Modern Python development with Python 3.12+, Django, FastAPI, async patterns,

performing-yara-rule-development-for-detection

16
from plurigrid/asi

Develop precise YARA rules for malware detection by identifying unique byte patterns, strings, and behavioral indicators in executable files while minimizing false positives.

backend-development

16
from plurigrid/asi

Backend API design, database architecture, microservices patterns, and

review-current-branch

16
from shibayu36/config-file

シニアソフトウェアエンジニアとして現在のブランチのプルリクエストをレビューする

spec-first-development

16
from woojubb/robota

Use before implementing any change that adds, removes, or modifies package behavior, public API, types, or contracts. Ensures the governing spec is updated before code is written and a verification test plan exists.

plugin-development

16
from woojubb/robota

Guide plugin development workflows with validation, disable strategies, and error handling. Use when working on plugin development, plugin system changes, or plugin options validation.

branch-guard

16
from woojubb/robota

Guard against committing directly to protected branches (main, master, develop). Use before every git commit to ensure work happens on a feature branch.

create-branch

16
from JetBrains/databao-cli

Create a feature branch following project naming conventions. Use when starting work on a ticket, after understanding the scope, or when the agent needs to branch off main for new work.

spec-driven-development

15
from re-cinq/wave

Expert specification-driven development including TDD/BDD integration, living documentation, specification-to-code workflows, and validation strategies

cross-platform-development

15
from niklam/iracedeck

Use when working with native dependencies, handling platform differences, or when build/install/test issues arise on non-Windows platforms

test-driven-development

14
from jay6697117/cx-switch

Use when implementing any feature or bugfix, before writing implementation code

subagent-driven-development

14
from jay6697117/cx-switch

Use when executing implementation plans with independent tasks in the current session