iop098321qwe/nbccpr
dot_config/opencode/skills/nbccpr/SKILL.md
Create and push Conventional Commit branches when the prompt contains `nbccpr` or `NBCCPR`. Use when the user specifies a branch type (feature, bugfix, release, hotfix) and needs a new branch created, changes committed with Conventional Commit headers plus descriptive bodies, and the branch pushed to the remote repository.
testing
Updated Apr 23, 2026
$ install --global
skillsauthnpx skillsauth add iop098321qwe/dotfiles-arch nbccprInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 1:03 PM25.5s13 files scanned
SKILL.md
- name:
- nbccpr
- description:
- >-
NBCCPR Branch + Commit Workflow
Parse the command
- Detect
nbccprorNBCCPRin the prompt; treat it as an explicit request to create a branch, commit, and push. - Expect syntax:
nbccpr <type> [branch-name] [task context]. - Accept types:
feature,bugfix,release,hotfix. - Treat the next token (or quoted string) after
<type>as the branch name when it is provided. Any remaining text is task context, not part of the branch name. - If no branch name is provided, generate one automatically from task context
when available. If there is no task context, generate the slug from the
intended Conventional Commit header description after inspecting the
changes. If that is still empty, fall back to
auto-update. - Explicit branch names always override auto-generation.
- If the branch name already includes a valid prefix (for example,
feature/add-login), reuse it only if the prefix matches<type>; otherwise ask for clarification. - Slugify the branch name to lowercase kebab-case (ASCII only). Replace
spaces or underscores with
-, drop punctuation, collapse repeats, and trim leading or trailing-.
Choose the base branch
- Use
developforfeature,bugfix, andrelease. - Use
mainforhotfix. - If the required base branch does not exist locally or remotely, stop and ask.
Create and switch the branch
- Fetch remote refs if available (
git fetch origin) and check out the base branch. - Ensure the base branch is up to date (
git pull --ff-only). - Create and switch to the new branch:
git switch -c <type>/<slug>. - If the working tree is dirty and switching branches fails, ask whether to stash, commit, or proceed from the current branch.
Commit with Conventional Commits
- Follow the
conventional-commitsskill for type, scope, and header format. - Stage relevant changes only (
git add ...). - When changes include
AGENTS.mdorREADME.md(any path), create a separatedocsConventional Commit that contains only those files. Stage them separately and do not combine them with non-doc changes. - Never edit or stage
CHANGELOG.md. If it is modified, stop and ask for the release process or tooling that updates it; do not include it in commits. - Do not create empty commits.
- Include a short descriptive body (1-2 sentences) that explains intent or impact, not just the file changes.
Push the branch
- Push with upstream tracking:
git push -u origin <type>/<slug>. - If
originis missing, ask for the correct remote name. - Report any push failures and stop.
Related Skills
iop098321qwe/skill-creator
tools
VerifiedTrustedCommunity
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
SKILL.mdUpdated Apr 23, 2026
iop098321qwe/markdown-editor
testing
VerifiedTrustedCommunity
Edit or update Markdown files (.md) following best practices and industry standards. ALWAYS use for any .md edit or review, even if the user does not explicitly request it, unless the file is inside a directory that contains a .obsidian/ folder (treat as Obsidian vault and do not use this skill).
SKILL.mdUpdated Apr 23, 2026
iop098321qwe/conventional-commits
data-ai
VerifiedTrustedCommunity
Apply Conventional Commits for git and GitHub work. Use for creating or naming branches, composing commit messages, writing PR titles and bodies, preparing release notes, or standardizing git and GitHub metadata.
SKILL.mdUpdated Apr 23, 2026
iop098321qwe/agents-md-writer
development
VerifiedTrustedCommunity
Create, update, and refine AGENTS.md files for a codebase. Always trigger when any command runs in a repo that contains AGENTS.md, even if AGENTS.md is not referenced. Use when asked to write agent instructions, repo handoff guides, or project operating manuals, when aligning AGENTS.md with the current code, or whenever any AGENTS.md exists anywhere in the repo (must verify). Enforce a fixed section order, 80-character line limits (with documented exceptions), best practices and industry standards, and Conventional Commits when drafting commit messages. Always run a self-audit after code changes to keep AGENTS.md current.
SKILL.mdUpdated Apr 23, 2026