agentleFS
nasanasa/fprime/.github/skills/fprime-checklist-implementation/SKILL.md

fprime-checklist-implementation

Skill12k starsChanged 21 months agoApache-2.0View on GitHub

Implementation-stage pass of the F Prime Component Development Checklist. Run after the C++ implementation and unit tests exist: re-runs fprime-auto-checklist against the previous checklist, decides the Implementation (section 3) and Unit Testing (section 4) review rows, and re-decides any earlier decision the tool flags STALE because the SDD or model changed since. Keywords: F Prime, checklist, implementation stage, unit test, ISR, units in names, boundary tests, fprime-auto-checklist.

  • Installs packages

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 22 mentionsJun 2026: 3 mentionsJul 2026: 7 mentionsAug 2026: 2 mentionsSep 2026: 7 mentionsOct 2026: 11 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the nasa/fprime repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about nasa/fprime

The biggest 5 of 71 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 71

Talked about on GitHub, YouTube, Hacker News and the web (71 times).

On GitHub · 50

45 more on GitHub

On YouTube · 13

8 more on YouTube

On the web · 2

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run against the previous checklist:

    line 39
  2. Very specific:

    YES: no note. The tool's own rule pointer (R8 pass, ` cpp/fprime/no-printf 0 findings ) is the only text a YES row carries.

    line 77
  3. Very specific:

    Never run fprime-util check, coverage, topology builds or hardware steps from this skill.

    line 94

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Checklist — implementation stage

Updates the component's docs/checklist.md after the implementation and unit tests are written. The tool recomputes every tool-decided row (now with the code present), carries the design-stage decisions, and queues what this stage must decide. It performs no development step: unit-test runs, coverage and leak checks are read from what fprime-util check --coverage already left behind (coverage/summary.txt), never produced here.

Procedure

  1. Install the tool from a clone (the clang-tidy plugin is built from the clone, it is not in the pip package); without the plugin every static-analysis row (31 of them) comes back UNCHECKED, so do not skip it:

    git clone https://github.com/LeStarch/fprime-auto-checklist && cd fprime-auto-checklist
    pip install -e .
    sudo apt-get install -y clang-tidy-15 llvm-15-dev libclang-15-dev   # LLVM 15 (plugin and clang-tidy must match)
    cmake -S native -B native/build -DClang_DIR=/usr/lib/llvm-15/lib/cmake/clang && cmake --build native/build
    cd -   # back to the project root; run the tool from there

    A prebuilt plugin is picked up from $FPRIME_TIDY_PLUGIN (--tidy-plugin), clang-tidy from $CLANG_TIDY (--clang-tidy).

  2. Run against the previous checklist:

    fprime-auto-checklist run --module <Path/To/Component> --analyzer clang-tidy \
        --stage implementation --previous <Path/To/Component>/docs/checklist.md \
        -o <Path/To/Component>/docs/checklist.md

    The queue (Hand-off section, checklist.json → queue) contains:

    • review: section-3/4 rows the tool leaves to a reviewer — 3.21 (CL-1 ISR state before enable), 3.23 (CL-2 interrupt enables cleared at init), 3.33 (CL-3 units in names), 3.38 (CL-4 implementation matches requirements and design), 4.3 (CL-5 boundary tests);
    • stale: design-stage decisions whose inputs changed — the SDD (section 1) or the SDD/FPP model (section 2) differ from what was reviewed. Their status is kept but flagged STALE:; re-decide them against the current text.
  3. Apply each rule verbatim against the code (*.cpp/*.hpp), the FPP model and test/ut/. For CL-4 walk the requirements table row by row and name the handler that satisfies each; for CL-5 list the bounded quantities (array sizes, FW_ASSERT limits, config constants, argument ranges) and the test that exercises the limit and one past it.
  4. Record with decide (--status YES|NO|N/A, a one-line --note (file:line, requirement id or test name); --from for a batch). Stale rows are recorded the same way; the new decision replaces the old one and is stamped with the current fingerprint.
  5. Re-run step 1 and confirm Nothing to review at the implementation stage. Report the totals line, every NO with its note, and the UNCHECKED rows that wait on a process step not yet performed (coverage, leak check, topology build, CI) — say which step, do not perform it.

Notes discipline

The rendered table is read by people; keep it sparse.

  • YES: no note. The tool's own rule pointer (R8 pass, `cpp/fprime/no-printf` 0 findings) is the only text a YES row carries; your --note (one clause, the ids you checked) is stored in the JSON for traceability and is not rendered.
  • NO: one line, what is wrong and where — file:line, requirement id or table — and the fix in a few words. No requirement-by-requirement walks, no restating the tool's finding, no "Confirmed:" prefixes.
  • N/A: one clause stating why the item does not apply.
  • UNCHECKED: name the process step that has not been performed.
  • Audits that confirm the tool's verdict are silent in the table; an override renders as one Audit (...) line from your --note.

Rules

  • docs/checklist.md stays beside docs/sdd.md; the SDD's last line is Component Development Checklist: [checklist.md](checklist.md) — restore it if an SDD edit dropped it.
  • Decide only queued rows; tool-decided rows are audited at close-out.
  • A STALE row is re-read in full, not re-confirmed from its old note.
  • Never run fprime-util check, coverage, topology builds or hardware steps from this skill; --build is reserved for an operator who asks for it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.