@feniix/pi-devtools

Devtools extension for pi — branch and PR workflow, release automation, PR feedback resolution, merge commands, with GitHub and Linear tracker support

Packages

Package details

extensionskillprompt

Install @feniix/pi-devtools from npm and Pi will load the resources declared by the package manifest.

npm repohome report
$ pi install npm:@feniix/pi-devtools
Package
@feniix/pi-devtools
Version
3.1.1
Published
Jul 12, 2026
Downloads
250/mo · 129/wk
Author
feniix
License
MIT
Types
extension, skill, prompt
Size
89.4 KB
Dependencies
0 dependencies · 3 peers
Pi manifest JSON
{
  "extensions": [
    "./extensions/index.ts"
  ],
  "skills": [
    "./skills"
  ],
  "prompts": [
    "./prompts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

@feniix/pi-devtools

Devtools extension for pi — branch and PR workflow, release automation, and merge commands.

Features

  • Git Workflow Tools: Create branches, commit, push, create PRs
  • Merge Commands: Merge or squash-merge PRs with observable, worktree-safe branch cleanup
  • Release Automation: Analyze commits, bump versions, generate changelogs, create releases
  • CI Status Checking: Check GitHub Actions status before merging or releasing

Install

pi install npm:@feniix/pi-devtools

Ephemeral (one-off) use:

pi -e npm:@feniix/pi-devtools

Active Working Directory and Worktrees

Every tool runs Git, GitHub CLI, and repository-relative file operations in Pi's active working directory (active cwd), not the extension process directory. devtools_get_repo_info reports the active worktree root, linked worktree context, detached HEAD state, Git directories, and all parsed worktree records.

When merge cleanup is requested, remote and local cleanup are attempted and reported separately. Occupied branches are retained when checked out by the active or another linked worktree, including locked or conservatively retained prunable records. A retained branch or cleanup failure does not change a successful merge into a failed merge.

The extension observes worktree topology for safety, but it will never create, remove, unlock, or prune worktrees. It also does not switch to or update the default branch after a merge.

Tools

Branch & PR Tools

Tool Description
devtools_create_branch Create and switch to a new git branch
devtools_commit Stage files and create a commit with conventional format
devtools_push Push branch to remote with upstream tracking
devtools_create_pr Create a GitHub pull request
devtools_get_repo_info Get active worktree, linked/detached context, default branch, and status

Merge Tools

Tool Description
devtools_merge_pr Merge a PR with optional best-effort remote and local branch cleanup
devtools_squash_merge_pr Squash-merge a PR with optional best-effort remote and local branch cleanup
devtools_check_ci Check CI status for a PR or the current branch

Release Tools

Tool Description
devtools_get_latest_tag Get the latest version tag from git
devtools_analyze_commits Analyze commits since last tag to determine version bump
devtools_bump_version Update version in package.json
devtools_create_release Create a GitHub release with changelog

Skills

  • brpr: Branch, commit, push, and open PR workflow
  • release: Automated release process with changelog generation
  • merge: Merge or squash-merge PRs

Configuration

Required: GitHub CLI

The gh CLI must be installed and authenticated:

gh auth login

Optional: Default Branch

The extension auto-detects the default branch, but you can set it explicitly:

export DEFAULT_BRANCH=main  # or 'master'

Requirements

  • pi v0.51.0 or later
  • git CLI
  • gh CLI (authenticated)
  • jq (for JSON parsing)

License

MIT