📦

birdview

Name: birdview
Author: qiuner

Revisão do conteúdo r1 Seguro ⚙️ Comandos externos⚡ Contém scripts📁 Acesso ao sistema de arquivos🌐 Acesso à rede🔑 Variáveis de ambiente

Map Architecture Before You Change Code

Complex repositories hide ownership, constraints, and change impact. Birdview builds evidence-linked maps and reviewable implementation scopes before coding begins.

Suporta: Claude Codex Code(CC)

📊 76 Adequado

Pare e solicite confirmação antes de instalar.

Revise o plano e obtenha o consentimento explícito do usuário antes de alterar arquivos.

Instalar com meu Agente

Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.

Solicitação do agente

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

Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.

Recursos legíveis por agentes

Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.

Detalhe em Markdown GET /skills/qiuner-birdview.md manifest assinado GET /api/skills/qiuner-birdview/manifest lockfile assinado GET /api/skills/qiuner-birdview/lockfile

Testar

Usando "birdview". Map the authentication flow without changing code.

Resultado esperado:

An HTML architecture view showing authentication modules and relationships.
Source-linked evidence for each mapped responsibility.
Coverage notes and unresolved architecture questions.

Usando "birdview". Plan a cache invalidation change with Birdview.

Resultado esperado:

A change view highlighting current and proposed module impact.
A list of affected files, applicable constraints, and verification steps.
A confirmation request before implementation begins.

Usando "birdview". Build a complete constraint inventory for the API directory.

Resultado esperado:

A reviewed constraint graph grouped by topic and directory.
Source ranges, applicability decisions, and unresolved conflicts.
An explicit statement of checked coverage and remaining gaps.

Auditoria de segurança

Seguro

v1 • 22/09/2026 Abrir o relatório versionado

All 400 presented static findings are false positives after contextual review; they arise from generated assets, translated documentation, safe rendering, and explicit CLI, build, or test operations. No prompt injection, credential collection, covert network transfer, or malicious intent was found in the reviewed evidence, but 2,774 capped static matches remain outside this adjudication. Static review was capped at 400/3174 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

167

Arquivos analisados

21,593

Linhas analisadas

Itens de revisão

Falsos positivos ignorados

Fatores de risco

⚙️ Comandos externos (50)

⚡ Contém scripts (50)

📁 Acesso ao sistema de arquivos (50)

🌐 Acesso à rede (50)

docs/index.html:15 docs/index.html:24 docs/index.html:52 docs/index.html:57 docs/index.html:61 docs/index.html:63 docs/installation.md:24 docs/installation.zh.md:24 docs/site.js:92 docs/site.js:97 examples/architecture.json:15 examples/harness-activity.html:272 package-lock.json:29 package-lock.json:46 package-lock.json:63 package-lock.json:80 package-lock.json:97 package-lock.json:114 package-lock.json:131 package-lock.json:148 package-lock.json:165 package-lock.json:182 package-lock.json:199 package-lock.json:216 package-lock.json:233 package-lock.json:250 package-lock.json:267 package-lock.json:284 package-lock.json:301 package-lock.json:318 package-lock.json:335 package-lock.json:352 package-lock.json:369 package-lock.json:386 package-lock.json:403 package-lock.json:420 package-lock.json:437 package-lock.json:454 package-lock.json:471 package-lock.json:478 package-lock.json:488 package-lock.json:500 package-lock.json:505 package-lock.json:547 package-lock.json:554 package-lock.json:560 package-lock.json:564 package-lock.json:571 package-lock.json:586 package-lock.json:593

🔑 Variáveis de ambiente (27)

A auditoria estática e semântica concluída mais recente não detectou achados de segurança confirmados. Isso não comprova que a skill não tenha efeitos colaterais.

Auditado por: codex

Compartilhar e citar este relatório

Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.

Abrir o relatório versionado

Copiar link do relatório

https://skillstore.io/skills/qiuner-birdview/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/qiuner-birdview/security.svg)](https://skillstore.io/skills/qiuner-birdview?utm_source=security_passport_badge)

Badge HTML

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

Cartão incorporável

<iframe src="https://skillstore.io/embed/skills/qiuner-birdview.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citações acadêmicas (APA · BibTeX · CFF)

Citação APA

qiuner. (2026). birdview security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/qiuner-birdview/audits/1

Citação BibTeX

@techreport{qiuner-qiuner-birdview-2026,
  author = {qiuner},
  title = {birdview security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/qiuner-birdview/audits/1},
  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: "birdview security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "qiuner"
date-released: "2026-09-22"
url: "https://skillstore.io/skills/qiuner-birdview/audits/1"
identifiers:
  - type: other
    value: "skillstore:qiuner-birdview:audit:1"
    description: "Skillstore immutable audit report identifier"

Pontuação do Skillstore

Por que esta pontuação Confiança das evidências: Médio

Arquitetura

Manutenibilidade

Conteúdo

Comunidade

Conformidade com a especificação

O que você pode criar

Understand an unfamiliar repository

Create an evidence-linked architecture map before selecting files or proposing changes.

Review an AI change plan

See affected modules, files, constraints, and verification steps before authorizing implementation.

Trace repository constraints

Collect local instructions, review applicability, and connect approved rules to architecture modules.

Teste estes prompts

Map this repository

Use Birdview to map this repository. Do not edit code. Show the HTML preview, source evidence, coverage, and uncertainties.

Review project constraints

Use Birdview to discover and review effective constraints for [scope]. Show source coverage, applicability, conflicts, and unresolved gaps.

Plan a focused change

Use Birdview to plan [change]. Map the current architecture, identify affected modules and files, include applicable constraints, and wait for confirmation.

Assess architecture and refactoring

Use Birdview to evaluate [subsystem]. Separate evidence from inference, identify structural risks, propose staged refactoring scopes, and define verification for each stage.

Boas práticas

Start with a specific repository scope and state whether you need architecture, constraints, or a change plan.
Review the rendered HTML, evidence links, uncertainty markers, and coverage notes before accepting the map.
Refresh the map when responsibilities, relationships, constraints, or planned modules materially change.

Evitar

Do not treat a valid schema as proof that module ownership or architectural claims are correct.
Do not use example maps or unreviewed source text as evidence for the current repository.
Do not start implementation before reviewing and confirming the displayed change scope unless confirmation is explicitly waived.