spec-ops-method/Spec Ops Action

Automatically create GitHub issues when specification files change. Supports spec-first workflows.

Trust Signals

name	description	required	default
file-pattern	Glob pattern(s) for specification files	no	*/specification*.md
file-patterns	Alternative: array of multiple glob patterns (one per line)	no	—
exclude-pattern	Glob pattern(s) for files to exclude	no	—
case-sensitive	Whether file pattern matching is case-sensitive	no	false
issue-title-template	Template for issue title	no	Specification Change: {{ filename }}
issue-body-template	Path to a markdown template file for issue body, or inline template	no	—
include-diff	Whether to include the file diff in the issue body	no	true
diff-context-lines	Number of context lines to include in diff	no	3
max-diff-lines	Maximum lines of diff to include (truncate with note if exceeded)	no	500
include-file-link	Whether to include a link to the changed file	no	true
include-commit-link	Whether to include a link to the triggering commit	no	true
include-pr-link	Whether to include a link to the PR (if triggered by PR)	no	true
sanitize-diff	Escape/sanitize diff content to avoid rendering raw HTML/markdown	no	true
labels	Comma-separated list of labels to apply to created issues	no	spec-change
assignees	Comma-separated list of GitHub usernames to assign	no	—
milestone	Milestone number or name to associate with issues	no	—
create-on-new-files	Create issues when new specification files are added	no	true
create-on-deleted-files	Create issues when specification files are deleted	no	true
dry-run	Log what would be created without actually creating issues	no	false
github-token	GitHub token for API access	no	${{ github.token }}

name	description
issues-created	JSON array of issue numbers that were created
issues-count	Number of issues created
files-detected	JSON array of specification files that were detected as changed
files-count	Number of specification files detected