New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Close Task Commit Push PR

by devoxx in devoxx/DevoxxGenieIDEAPlugin

Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request.

MITAuto-check: notesDevelopment

Install Close Task Commit Push PR

skills CLI
$ npx skills add devoxx/DevoxxGenieIDEAPlugin --skill close-task-commit-push-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install devoxx/DevoxxGenieIDEAPlugin close-task-commit-push-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/devoxx/DevoxxGenieIDEAPlugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/close-task-commit-push-pr .claude/skills/close-task-commit-push-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
close-task-commit-push-pr
GitHub stars
684
Token cost
~1k tokens
SKILL.md length
526 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request.

  • Works in 9 steps: Identify the task → Close the backlog task → Analyze changes and plan commits → …
  • The user says close task and ship it
  • SKILL.md covers Context, Your task and Rules
  • Calls git and gh; reaches claude.com

What it does

Close Task Commit Push PR is an agent skill from devoxx/DevoxxGenieIDEAPlugin. Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with OpenAI, Git and Model Context Protocol. The repository describes itself as: DevoxxGenie is an agentic plugin for IntelliJ IDEA that uses local LLM's (Ollama, LMStudio, GPT4All, Jan and Llama.cpp) and Cloud based LLMs to help review, test, explain your… The licence is MIT.

When your agent uses it

  • The user says close task and ship it
  • Close task commit push pr
  • Invokes /close-task-commit-push-pr

Example prompts

  • “close task and ship it”
  • “close task commit push pr”
  • “/close-task-commit-push-pr”

Requirements

  • Pre-approved tools (allowed-tools): Bash(git add:*), Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git commit:*), Bash(git push:*), Bash(git branch:*), Bash(git checkout:*), Bash(gh pr create:*), mcp__backlog__task_edit, mcp__backlog__task_complete, mcp__backlog__task_view

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Identify the task
  2. Close the backlog task
  3. Analyze changes and plan commits
  4. Commit
  5. Push
  6. Pull Request
  7. Update task with PR reference
  8. Amend commit with updated task file
  9. Report

What it can do on your machine

Read from SKILL.md and the folder at commit dd1baf5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git add:*)
    • Bash(git status:*)
    • Bash(git diff:*)
    • Bash(git log:*)
    • Bash(git commit:*)
    • Bash(git push:*)
    • Bash(git branch:*)
    • Bash(git checkout:*)
    • Bash(gh pr create:*)
    • mcp__backlog__task_edit

    …and 2 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • claude.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Close Task Commit Push PR loads about 1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 526 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:49
    names (never `git add -A`; never stage `.env` or credential files).

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from devoxx/DevoxxGenieIDEAPlugin at commit dd1baf5, republished under its MIT licence (© devoxx). 526 words, ~1,047 tokens.

Download SKILL.mdSave it as .claude/skills/close-task-commit-push-pr/SKILL.md (or your agent's skills folder).
name
close-task-commit-push-pr
description
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
allowed-tools
Bash(git add:*), Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git commit:*), Bash(git push:*), Bash(git branch:*), Bash(git checkout:*), Bash(gh pr create:*), mcp__backlog__task_edit, mcp__backlog__task_complete, mcp__backlog__task_view

Close Task, Commit, Push & PR

Context

  • Current git status: !git status
  • Current git diff (staged and unstaged changes): !git diff HEAD
  • Current branch: !git branch --show-current
  • Main branch: !git rev-parse --verify main 2>/dev/null && echo main || echo master
  • Recent commits: !git log --oneline -10

Your task

Close the active backlog task, commit all changes, push, and open a pull request.

Step 0 — Identify the task
  • Extract the task ID from the current branch name (e.g. feature/task-113-split-css-modules → task-113).
  • If no task ID is found in the branch name, ask the user which task to close.
Step 1 — Close the backlog task

Close the task before committing so the task file changes are included in the commit and PR.

  • Use mcp__backlog__task_view to read the task details (title, acceptance criteria).
  • Use mcp__backlog__task_edit to:
    • Set status to Done
    • Check off all acceptance criteria that were completed (review the diff to determine which ones)
    • Write a finalSummary that concisely describes what was implemented
  • Use mcp__backlog__task_complete to move the task to the completed folder.
Step 2 — Analyze changes and plan commits

Before committing, analyze git status and git diff HEAD to identify logically distinct groups of changes. Group by feature or concern — for example:

  • New files that form a self-contained module → one commit
  • Modifications to an existing file that depend on the new module → separate commit
  • Task/backlog file changes → include in the final commit (or a dedicated chore commit)

Print a short commit plan (list of planned commits with the files in each) so the grouping is visible.

Step 3 — Commit
  • Create one commit per logical group identified above. Stage only the files for that group using explicit file names (never git add -A; never stage .env or credential files).
  • Write a clean, descriptive commit message for each commit using conventional commits style.
  • End every commit message with: Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
  • Use a HEREDOC to pass the commit message for correct formatting.
  • Include the closed task file in the final commit.
Show full SKILL.md (198 more words)Show less
Step 4 — Push
  • If the current branch is main or master, create a new feature branch first (use a descriptive name based on the changes).
  • Push the branch to origin with -u to set upstream tracking.
Step 5 — Pull Request
  • Create a PR using gh pr create targeting the main branch.
  • Keep the PR title short (under 70 characters), using conventional commit style.
  • Use a HEREDOC for the PR body with this format:
## Summary
<1-3 bullet points describing the changes>

## Test plan
- [ ] <testing checklist items>

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Step 6 — Update task with PR reference
  • Now that you have the PR number, use mcp__backlog__task_edit to append the PR URL/number to the finalSummary.
Step 7 — Amend commit with updated task file
  • Stage the updated task file and amend the last commit to include the PR reference: git commit --amend --no-edit then git push --force-with-lease.
Step 8 — Report
  • Print the PR URL and confirm the task was closed.

Rules

  • Do all steps in as few messages as possible. Parallelize independent tool calls.
  • Do not read or explore code beyond what git provides in the context above.
  • Do not use interactive git flags (-i).
  • Never force-push or amend existing commits.
  • If a pre-commit hook fails, fix the issue and create a NEW commit (do not amend).

© devoxx, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/close-task-commit-push-pr of devoxx/DevoxxGenieIDEAPlugin.

Open the folder on GitHubat commit dd1baf5

Compare with similar skills

Close Task Commit Push PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Close Task Commit Push PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Close Task Commit Push PR this skilldevoxx/DevoxxGenieIDEAPlugin684—~1kAutomated safety check: NotesMIT
Open Code Review CLIalibaba/open-code-review44k—~3.1kAutomated safety check: PassApache-2.0
Zhtw Conventionssysprog21/zhtw-mcp488—~2kAutomated safety check: PassMIT
PR Review Feedback Handlergittower/git-flow-next458—~2.9kAutomated safety check: NotesCustom licence
GitHub Commentingjuspay/neurolink143—~698Automated safety check: PassMIT
GitHubswarmclawai/swarmclaw687—~820Automated safety check: PassMIT

Similar skills

  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    44k GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Zhtw Conventions

    sysprog21/zhtw-mcp

    The zhtw-mcp conventions no gate enforces - the register a comment, a commit message and a PR reply are written in, where Chinese belongs in the tree and where it does not, the untracked working…

    488 GitHub stars~2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • PR Review Feedback Handler

    gittower/git-flow-next

    Fetches review comments on a pull request, judges each one, writes the evaluation to a plan file and implements accepted changes, waiting for approval before anything public.

    458 GitHub stars~2.9k tokensUpdated 29 days ago
    DevelopmentAuto-check: notes

  • GitHub Commenting

    juspay/neurolink

    How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules.

    143 GitHub stars~698 tokensUpdated today
    DevelopmentAuto-check passed

  • GitHub

    swarmclawai/swarmclaw

    GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.

    687 GitHub stars~820 tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Repo Repair

    oaslananka/kicad-mcp-pro

    A skill your agent uses for maintainer-requested pull request repairs in kicad-mcp-pro; maps changes to repository-native validation gates and safety constraints.

    119 GitHub stars~581 tokensUpdated today
    DevelopmentAuto-check passed

More from devoxx/DevoxxGenieIDEAPlugin

  • Git Commit Push PR

    devoxx/DevoxxGenieIDEAPlugin

    Commit all changes, push to remote, and open a pull request in one go.

    684 GitHub stars~698 tokensUpdated 8 days ago
    Auto-check: notes

  • Release

    devoxx/DevoxxGenieIDEAPlugin

    Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR…

    684 GitHub stars~1.7k tokensUpdated 8 days ago
    Auto-check passed

  • Start Task

    devoxx/DevoxxGenieIDEAPlugin

    Create a feature branch for a backlog task, switch to it, and start implementation.

    684 GitHub stars~792 tokensUpdated 8 days ago
    Auto-check passed

  • Review

    devoxx/DevoxxGenieIDEAPlugin

    Review local code changes for bugs, regressions, missing tests, and pragmatic improvements.

    684 GitHub stars~652 tokensUpdated 8 days ago
    Auto-check passed

Works with

Categories

Questions about Close Task Commit Push PR

What does Close Task Commit Push PR do?

Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Close Task Commit Push PR is an agent skill from devoxx/DevoxxGenieIDEAPlugin. Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request.

When should I use Close Task Commit Push PR?

Close Task Commit Push PR fits situations like: the user says close task and ship it; close task commit push pr; invokes /close-task-commit-push-pr.

How do I install Close Task Commit Push PR in Claude Code?

Run `npx skills add devoxx/DevoxxGenieIDEAPlugin --skill close-task-commit-push-pr -a claude-code`. Or copy the skill folder (.claude/skills/close-task-commit-push-pr in devoxx/DevoxxGenieIDEAPlugin) into .claude/skills/close-task-commit-push-pr in your project. Claude Code loads it when a task matches its description.

How do I install Close Task Commit Push PR in Codex?

Run `npx skills add devoxx/DevoxxGenieIDEAPlugin --skill close-task-commit-push-pr -a codex`. Or copy the skill folder (.claude/skills/close-task-commit-push-pr in devoxx/DevoxxGenieIDEAPlugin) into .agents/skills/close-task-commit-push-pr in your project. Codex loads it when a task matches its description.

Can I use Close Task Commit Push PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add devoxx/DevoxxGenieIDEAPlugin --skill close-task-commit-push-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/close-task-commit-push-pr, .gemini/skills/close-task-commit-push-pr, .github/skills/close-task-commit-push-pr and .opencode/skills/close-task-commit-push-pr in your project.

What does Close Task Commit Push PR need to run?

Going by SKILL.md and its folder, Close Task Commit Push PR needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash(git add:*), Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git commit:*), Bash(git push:*), Bash(git branch:*), Bash(git checkout:*), Bash(gh pr create:*), mcp__backlog__task_edit, mcp__backlog__task_complete, mcp__backlog__task_view.

Does Close Task Commit Push PR access the network?

SKILL.md names 1 domain. In commands or code: claude.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Close Task Commit Push PR safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Close Task Commit Push PR use?

Close Task Commit Push PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Close Task Commit Push PR use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Close Task Commit Push PR?

Skills that share tags, products or a category with Close Task Commit Push PR: Open Code Review CLI (alibaba/open-code-review, 44k stars), Zhtw Conventions (sysprog21/zhtw-mcp, 488 stars), PR Review Feedback Handler (gittower/git-flow-next, 458 stars) and GitHub Commenting (juspay/neurolink, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Close Task Commit Push PR?

devoxx (a GitHub organization) maintains it in devoxx/DevoxxGenieIDEAPlugin, which has 684 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 29, 2026.

Source: devoxx/DevoxxGenieIDEAPlugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.