Skills business-conflict-analyzer
๐Ÿ“ฆ

business-conflict-analyzer

Content revision r1 High Risk โš™๏ธ External commands๐Ÿ“ Filesystem access๐Ÿ”‘ Env variablesโšก Contains scripts๐ŸŒ Network access

Analyze Breaking Changes Before You Commit

Contract and schema changes can break downstream services, clients, and data flows. This skill maps affected references and produces a business impact report before commit.

Supports: Claude Codex Code(CC)
โš ๏ธ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "business-conflict-analyzer" from https://skillstore.io/skills/gobeyondyang-business-conflict-analyzer.md and its manifest at https://skillstore.io/api/skills/gobeyondyang-business-conflict-analyzer/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "business-conflict-analyzer". Rename UserDTO.mobile to phone and assess downstream impact.

Expected outcome:

  • Risk: High because existing consumers still reference the removed field.
  • Affected areas: service mappings, frontend profile views, tests, and stored data migration.
  • Recommendation: retain a compatibility field, update consumers, migrate data, and verify contracts before removal.

Using "business-conflict-analyzer". Change the orders endpoint from version one to version two.

Expected outcome:

  • Risk: Medium when the old route remains available during migration.
  • Affected areas: API clients, routing tests, documentation, monitoring, and deployment configuration.
  • Recommendation: add the new route, deprecate the old route, notify owners, and monitor adoption.

Using "business-conflict-analyzer". Drop a database column used by an event producer.

Expected outcome:

  • Risk: High because historical data and message consumers can lose required values.
  • Required actions: inventory references, backfill or archive data, version the event schema, and coordinate deployment order.

Security Audit

High Risk
v4 โ€ข 7/19/2026 Open versioned report

Most static alerts are false positives from Markdown, test fixtures, locale handling, fixed argv subprocess calls, and readable multilingual files. Confirmed risks include mutable remote fetches, out-of-repository scanning, persistent agent configuration changes, and a destructive repository-wide rollback directive. The skill also claims blanket authority for broad consumer edits, which is a high-confidence prompt injection risk.

22
Files scanned
5,440
Lines analyzed
12
Review items
0
False positives ignored

Confirmed security concerns (1)

High
Prompt Injection Attempt Detected
SKILL.md states, "AI knows it's authorized to fix all consumers" and says, "Do not ask the user per-consumer." This converts one acceptance into blanket authority for broad edits.
The text explicitly claims expanded authorization and suppresses per-consumer confirmation. The directive is clear and directly affects agent edit scope.
Capability review items (12)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
Path traversal sequence
for rel in ("../frontend", "../web", "../../frontend",
The analyzer deliberately searches ../frontend, ../web, and ../../frontend, crossing the selected repository boundary. This can read source from sibling directories without separate scope approval.
High
Ruby/shell backtick execution
| **โ†’ 2** โŒ | 1. `git checkout -- .` to discard changes. 2. Confirm rollback complete. |
The skill explicitly directs the agent to run git checkout -- . when the user rejects a proposal. That command discards all tracked working-tree changes, including unrelated work.
Medium
Python environment access
env_roots = os.environ.get("FRONTEND_ROOT", "")
FRONTEND_ROOT accepts path lists, including absolute paths, and those locations are recursively searched. A configured value can expand file access beyond the audited project.
Medium
Hidden file access
CONFIG_DIR="$PROJECT_DIR/.claude"
The installer targets .claude/settings.local.json, a hidden agent configuration file, to register a persistent executable hook. The behavior is disclosed but remains security-sensitive.
Medium
Python file write/append
with open(config_file, 'w', encoding='utf-8') as f:
The installer rewrites an existing agent settings file after adding a PreToolUse command. This persistent configuration change can affect later tool execution.
Medium
Hardcoded URL
- url: https://github.com/GoBeyondYang/skills/raw/main/skills/business-conflict-analyzer/scripts/dif
The fetch metadata automatically retrieves a companion file from the mutable main branch without a commit pin or integrity hash. Upstream changes therefore enter the skill trust boundary.
Medium
Hardcoded URL
- url: https://github.com/GoBeyondYang/skills/raw/main/skills/business-conflict-analyzer/scripts/imp
The fetch metadata automatically retrieves a companion file from the mutable main branch without a commit pin or integrity hash. Upstream changes therefore enter the skill trust boundary.
Medium
Hardcoded URL
- url: https://github.com/GoBeyondYang/skills/raw/main/skills/business-conflict-analyzer/scripts/rep
The fetch metadata automatically retrieves a companion file from the mutable main branch without a commit pin or integrity hash. Upstream changes therefore enter the skill trust boundary.
Medium
Hardcoded URL
- url: https://github.com/GoBeyondYang/skills/raw/main/skills/business-conflict-analyzer/scripts/lan
The fetch metadata automatically retrieves a companion file from the mutable main branch without a commit pin or integrity hash. Upstream changes therefore enter the skill trust boundary.
Medium
Hardcoded URL
- url: https://github.com/GoBeyondYang/skills/raw/main/skills/business-conflict-analyzer/scripts/com
The fetch metadata automatically retrieves a companion file from the mutable main branch without a commit pin or integrity hash. Upstream changes therefore enter the skill trust boundary.
Medium
Hardcoded URL
- url: https://github.com/GoBeyondYang/skills/raw/main/skills/business-conflict-analyzer/scripts/ins
The fetch metadata automatically retrieves a companion file from the mutable main branch without a commit pin or integrity hash. Upstream changes therefore enter the skill trust boundary.
Medium
Hardcoded URL
- url: https://github.com/GoBeyondYang/skills/raw/main/skills/business-conflict-analyzer/references/
The fetch metadata automatically retrieves a companion file from the mutable main branch without a commit pin or integrity hash. Upstream changes therefore enter the skill trust boundary.

Risk Factors

โš™๏ธ External commands (50)
๐Ÿ“ Filesystem access (21)
๐Ÿ”‘ Env variables (14)
โšก Contains scripts (3)
๐ŸŒ Network access (8)
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/gobeyondyang-business-conflict-analyzer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/gobeyondyang-business-conflict-analyzer/security.svg)](https://skillstore.io/skills/gobeyondyang-business-conflict-analyzer?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/gobeyondyang-business-conflict-analyzer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/gobeyondyang-business-conflict-analyzer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/gobeyondyang-business-conflict-analyzer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

gobeyondyang. (2026). business-conflict-analyzer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/gobeyondyang-business-conflict-analyzer/audits/4

BibTeX citation

@techreport{gobeyondyang-gobeyondyang-business-conflict-analyzer-2026, author = {gobeyondyang}, title = {business-conflict-analyzer security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/gobeyondyang-business-conflict-analyzer/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "business-conflict-analyzer security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "gobeyondyang" date-released: "2026-07-19" url: "https://skillstore.io/skills/gobeyondyang-business-conflict-analyzer/audits/4" identifiers: - type: other value: "skillstore:gobeyondyang-business-conflict-analyzer:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
77
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

Review API contract changes

Trace DTO, endpoint, and response changes to backend clients, frontend consumers, and compatibility requirements.

Plan database migrations

Assess DDL changes, existing data risks, service dependencies, and required rollout sequencing.

Coordinate cross-stack releases

Produce a shared impact report for services, web clients, tests, and business owners before approval.

Try These Prompts

Analyze current changes
Analyze my current Git changes. List breaking changes, affected consumers, migration needs, and recommended next steps. Do not modify files.
Review a field rename
Review the rename of [old field] to [new field] in [contract]. Find backend and frontend consumers. Propose backward-compatible migration steps.
Assess a schema release
Analyze the DDL and API changes since [revision]. Map data, service, message, and client impacts. Produce a phased rollout and rollback plan.
Audit staged changes for commit
Analyze staged changes only. Identify P0 and P1 risks, explain evidence, and provide decision options. Do not install hooks or discard changes.

Best Practices

  • Run analysis from the intended repository root and review every external scan path before execution.
  • Compare findings with compilation, tests, schema checks, and service-owner confirmation before approving changes.
  • Use pinned skill assets and review the report before applying compatibility fixes or installing the commit guard.

Avoid

  • Do not treat a clean report as proof that unsupported languages, generated code, or dynamic consumers are unaffected.
  • Do not approve repository-wide automatic fixes without reviewing the complete file list and intended scope.
  • Do not use broad rollback commands when unrelated working-tree changes may exist.

Frequently Asked Questions

Which languages and frameworks are supported?
It includes rules for Java, Kotlin, Python, TypeScript, JavaScript, Go, Vue, React, JSP, SQL, YAML, XML, and common web frameworks.
Does it modify my code?
Analysis scripts generate a report. The skill documentation also proposes optional fixes, rollback actions, and hook installation that require careful approval.
Can it block a Git commit?
Yes. The optional Claude Code hook runs the analyzer before git commit and blocks changes classified as P0.
Does it replace tests or compilation?
No. It uses heuristics and reference searches. Confirm important findings with builds, tests, contract validation, and owner review.
Where is the report saved?
The command-line pipeline writes conflict-report.md in the current project directory and can overwrite an existing file with that name.
Does it require network access?
The included scripts are local, but the skill frontmatter automatically fetches companion files from GitHub when loaded.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

536932510ff0a3e976ac88662d9e038a7faa088b

Maintenance freshness

7/20/2026

Usage

0 downloads ยท 0 views

View all