n8n-studio:finish

Generate result documentation, persist n8n workflow JSON, and open a GitHub PR.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-finish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-studio:finish
Source: https://github.com/icednut/n8n-studio/tree/main/skills/finish
Command: npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-finish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp__n8n-mcp__n8n_get_workflow, mcp__plugin_github_github__create_pull_request, mcp__plugin_github_github__create_branch, mcp__plugin_github_github__push_files.

What problem does it solve?

It solves the problem of turning completed n8n workflow verification into a consistent, review-ready deliverable with documentation, stored workflow JSON, and an automatic GitHub Pull Request.

Core Features & Use Cases

  • Completion documentation generation: Creates 04-result.md in the standardized docs folder with request type, workflow targets, change summary, and verification outcomes.
  • Workflow artifact handling: Downloads finalized n8n workflow JSON via n8n-mcp, stores it under workflow/[프로젝트명]/n8n/, and refreshes per-workflow node-structure summaries.
  • Webhook triggerDataFormat updating: Detects a Webhook-first workflow and updates triggerDataFormat by extracting the latest successful Happy Path output data without modification.
  • Git commit + GitHub PR automation: Stages docs, workflow JSON, and test outputs, commits with a feature-oriented message, pushes to the working branch, and creates a PR targeting main.
  • Use Case: After successful TDD development and integration verification, consistently package the final changes for maintainers and reviewers, including result reporting and workflow JSON backups.

Quick Start

Ask the assistant to run the completion phase by saying: "작업 마무리하고 PR까지 만들어줘."

Frequently Asked Questions about n8n-studio:finish

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

FAQPage Schema
How do I finalize an n8n workflow and create a GitHub PR automatically?

You can finalize an n8n workflow and create a GitHub PR by triggering the completion phase, which generates 04-result.md documentation, downloads workflow JSON artifacts via n8n-mcp, commits changes, and opens a pull request against the main branch.

What is included in the n8n workflow finalization documentation?

The n8n workflow finalization documentation includes a 04-result.md file containing the request type, workflow targets, change summary, and verification outcomes, alongside stored per-workflow node-structure summaries and updated Webhook triggerDataFormat data.

Does the n8n workflow PR creation process handle Webhook triggerDataFormat updates?

Yes, the n8n workflow PR creation process handles Webhook triggerDataFormat updates automatically by detecting Webhook-first workflows and extracting the latest successful Happy Path output data to update triggerDataFormat without modification during finalization.

Do I need n8n-mcp and GitHub plugins to automate workflow artifact persistence and PRs?

Yes, you need n8n-mcp and GitHub plugins to automate workflow artifact persistence and PRs, as the skill depends on n8n-mcp for downloading workflow JSON and GitHub plugins for creating branches, pushing files, and opening pull requests.

What's the best way to store n8n workflow JSON artifacts after test completion?

The best way to store n8n workflow JSON artifacts after test completion is using the finalization process to download them via n8n-mcp and save them under the workflow/[project]/n8n/ directory structure, ensuring consistent artifact backup.

Why does my n8n workflow PR need result reporting and summary JSON files?

Your n8n workflow PR needs result reporting and summary JSON files to provide maintainers with verification outcomes and node-structure context, as the 04-result.md and refreshed summary JSON ensure reviewers understand the workflow changes.