This skill should be used for configuring devloop project settings via .devloop/local.md, git workflow preferences, commit settings, review options
/plugin marketplace add Zate/cc-plugins/plugin install zate-devloop-plugins-devloop@Zate/cc-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Project-specific devloop settings via .devloop/local.md.
.devloop/local.md - NOT git-tracked (add to .gitignore)
YAML frontmatter followed by optional markdown notes:
---
# Git Workflow Settings
git:
auto-branch: false # Create branch when plan starts
branch-pattern: "feat/{slug}" # Branch naming pattern
main-branch: main # Name of main/trunk branch
pr-on-complete: ask # ask | always | never
# Commit Settings
commits:
style: conventional # conventional | simple
scope-from-plan: true # Use plan name as commit scope
sign: false # Sign commits with GPG
# Review Settings
review:
before-commit: ask # ask | always | never
use-plugin: null # Or: code-review, pr-review-toolkit
# GitHub Issues Integration (optional)
github:
link-issues: false # Enable GH issue linking in plans
auto-close: ask # ask | always | never - close issue on plan complete
comment-on-complete: true # Post completion summary to linked issue
---
# Project Notes
Local notes and context for this project...
When starting a new plan, automatically create a feature branch.
| Value | Behavior |
|---|---|
false | Stay on current branch (default) |
true | Create branch, ask for confirmation |
Pattern for auto-created branch names.
| Placeholder | Replaced With |
|---|---|
{slug} | Plan name slugified |
{date} | YYYY-MM-DD |
{user} | Git user name |
Examples:
feat/{slug} → feat/add-authentication{user}/{slug} → alice/add-authenticationWhen all plan tasks complete, create a PR.
| Value | Behavior |
|---|---|
ask | Ask user (default) |
always | Auto-create PR |
never | No PR prompt |
Commit message format.
| Value | Format |
|---|---|
conventional | type(scope): description |
simple | Plain description |
Run code review before committing.
| Value | Behavior |
|---|---|
ask | Ask user (default) |
always | Always review |
never | Skip review |
External plugin for code review.
| Value | Plugin |
|---|---|
null | Use devloop:code-reviewer (default) |
code-review | claude-plugins-official code-review |
pr-review-toolkit | claude-plugins-official pr-review-toolkit |
Enable GitHub Issues integration for issue-driven development.
| Value | Behavior |
|---|---|
false | No GH integration (default) |
true | Enable issue linking in plans |
When enabled:
/devloop:from-issue 123 starts work from an issue**Issue**: #123 headerAutomatically close linked issues when plan completes.
| Value | Behavior |
|---|---|
ask | Ask user (default) |
always | Auto-close issue |
never | Don't close issue |
Post a completion summary to the linked issue.
| Value | Behavior |
|---|---|
true | Post summary comment (default when link-issues is true) |
false | Don't comment |
Summary includes: tasks completed, time elapsed, archive location.
If no local.md exists, all settings use safe defaults:
git:
auto-branch: false
branch-pattern: "feat/{slug}"
main-branch: main
pr-on-complete: ask
commits:
style: conventional
scope-from-plan: true
sign: false
review:
before-commit: ask
use-plugin: null
github:
link-issues: false
auto-close: ask
comment-on-complete: true
---
git:
auto-branch: true
---
---
git:
auto-branch: true
branch-pattern: "feat/{slug}"
pr-on-complete: always
commits:
style: conventional
sign: true
review:
before-commit: always
use-plugin: pr-review-toolkit
---
---
git:
auto-branch: false
pr-on-complete: never
review:
before-commit: never
---
---
git:
auto-branch: true
pr-on-complete: always
github:
link-issues: true
auto-close: always
comment-on-complete: true
---
With this config:
/devloop:from-issue 123 fetches issue details**Issue**: #123 referenceThe devloop plugin reads config automatically. Commands like /devloop:ship parse .devloop/local.md and apply settings.
Internally, the plugin uses ${CLAUDE_PLUGIN_ROOT}/scripts/parse-local-config.sh to parse YAML frontmatter and return JSON with defaults filled in.
Edit .devloop/local.md directly. Changes take effect on next command.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.