Repository navigation
v0.8.0
Added
-
Path-scoped rules for contextual Claude Code guidelines (#20)
- Rules are markdown files with YAML frontmatter that apply selectively based on file path glob patterns
- Teams can define domain-specific guidelines (e.g., REST API standards for
src/api/**, React patterns forsrc/components/**) - Rules layer across project, personal, and team sources with automatic precedence handling
- Rules without
paths:frontmatter apply to all files - 5 starter rules included: security, testing, error handling, REST APIs, and React
- Rules sync to
~/.claude/rules/viastag sync stag sync --rules-onlyto sync only rules
-
Multi-source configuration for pulling configs from multiple repositories (#21)
source.languages,source.commands, andsource.skillsmaps in config to specify per-item sources- Items not explicitly configured fall back to
source.defaultrepository - Enables mixing team standards, community best practices, and specialized configs from different repos
- Graceful error handling: explicit sources warn on missing, default sources silently skip
-
Skills feature implementing the Agent Skills standard with Claude Code extensions (#22)
- Skills are parameterized, reusable workflows supporting tool restrictions, subagent execution, pre/post hooks, and model overrides
- Each skill is a directory with
SKILL.md(YAML frontmatter + markdown body) and optional supporting files - Skills accept arguments with defaults, options, and required/optional validation
stag skillscommand to list available skills with optional--tagfilteringstag skills <name>to show detailed skill infostag skills initto install starter skills (supports--projectand--claudeflags)stag sync --skills-onlyto sync only skills- 3 starter skills: code-review, security-audit, test-gen
- Skills sync to
~/.claude/skills/and are invocable via/skill-namein Claude Code - Multi-source support for sourcing skills from different repositories
-
Integration test framework for end-to-end testing (#16)
- Declarative YAML-based test fixtures for sync scenarios
- Test harness with fake GitHub client for deterministic testing
- Coverage for basic sync, provenance, languages, personal config, rules, multi-source, and skills