external-feedback-triage
Evaluate external technical feedback before acting. Use for reviews, scanner findings, blog advice, model suggestions, and recommendations whose applicability or evidence is uncertain.
v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 StelleMITsincronizzato 11 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/external-feedback-triageScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchettoe867dbe2…5b9e6ada
e867dbe25837…f1c15b9e6ada1 file · 2.0 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/AeonDave/malskill/tree/main/knowledge/external-feedback-triage@21cd568
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
Turn feedback into an evidence-backed disposition and complete the warranted work. A correct observation does not automatically justify the proposed remedy; a poor remedy does not invalidate the underlying defect.
Triage and act
- Separate the claims: identify the observed behavior, inferred cause/impact, and proposed change. Split mixed feedback into independently checkable items; consolidate duplicates without counting them as corroboration.
- Locate the current context: inspect the affected code or artifact, contract, version, configuration and existing decisions. Check nearby dependencies when they matter; a valid finding need not sit on a changed line.
- Test the claim: use the smallest meaningful inspection, reproduction or test. Assess impact and confidence separately; distinguish defects, preferences and optional improvements. A severity label or authoritative tone is not evidence. If direct verification is unavailable, preserve that uncertainty.
- Choose the disposition: use the table below. Check the proposed remedy against the actual cause, compatibility, edge cases and maintenance cost. Resolve contradictory suggestions against evidence and project requirements.
- Finish accepted work: apply the smallest sufficient fix within the task's authorization, then verify the affected behavior and relevant regressions. Continue independent accepted items while another needs clarification. Do not stop at a proposed patch when implementation is already requested.
- Report the outcome: state what was applied, adapted, deferred or rejected, why, and what evidence or check supports it. Name unresolved risk without inflating it. For several items, a compact disposition table can help.
| Disposition | Use when |
|---|---|
| Apply | The finding and remedy fit the current evidence, contract and task. |
| Adapt | The issue is real but the proposed fix breaks another requirement or misses the cause. |
| Defer | A potentially useful item needs evidence/access, belongs to later work, or exceeds the current task; give the revisit condition. |
| Reject | The claim is contradicted, inapplicable, or the suggested change has no justified benefit; cite the relevant evidence. |
| Clarify | A missing requirement or unresolved choice materially changes correctness, scope or authorization and cannot be established locally. |
Existing authorization remains valid. A request to review alone does not authorize implementation; a request to fix supported findings does not require another blanket approval. Honour explicit style preferences as preferences without inventing a technical defect.
Check the source-specific trap
| Input | Check that changes the decision |
|---|---|
| Code review | The requirement and affected behavior, including callers; avoid unrelated cleanup disguised as a necessary fix. |
| Scanner | Actual dependency/build, enabled code path and relevant preconditions; banners or a negative probe alone cannot settle applicability. |
| Advisory or PoC | Affected branch/configuration, backports, trigger and side effects; inspect external code before considering execution. |
| Model suggestion | Whether the referenced file, API and behavior actually exist. |
| Blog or tool advice | The documented version, environment and tradeoff behind the recommendation. |
Push back with evidence when a suggestion changes the wrong version, masks a failing test, weakens the contract, or solves a different problem. Do not dismiss a necessary boundary or abstraction merely because it has only one current caller.
Load evidence-before-claims when evidence is disputed or a claim exceeds the observation. Load verification-before-completion before claiming an applied fix complete. Use known-problem-hint-research when external evidence is the missing piece.
File di questa versione
- SKILL.md4.2 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 nov 2026 | 21cd568 | e867dbe2 | Firmata | – |
Altro da AeonDave
Tutto da questo editoreAltro in Report e compliance
Vai alla categoria- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login